Skip to content

VM create form: cannot add a disk until the page is refreshed once #3109

Closed

Description

Summary

On the VM create form, the "add disk" control does not work until the page is refreshed once. After a fresh navigation to the form, attempting to add a disk fails; a single manual page reload makes it work.

Reported on v1.4.2. The VM disk form has since been reworked substantially on main (see below), so this may already be resolved — this issue exists to pin the exact symptom and confirm it against current main before closing.

What changed since the report

The disk handling that shipped in v1.4.2 (VMDiskWidget, a one-shot useK8sList on mount with no refetch) has been replaced and hardened on main:

Those fixes target disk selection state. The reported symptom is about adding a disk array item (the array "+ Add" interaction) being unavailable until a refresh, which is a distinct facet — possibly already covered by the stale-RJSF-state fix, but not confirmed.

Repro / verification needed

  1. Fresh-navigate to the VM create form on current main.
  2. Without refreshing, try to add a disk.
  3. Confirm whether it works, or still requires one page reload.

If it still reproduces, narrow it to the array-field add interaction in SchemaForm and fix; if not, close as resolved by the SchemaForm rework.

Source

A user on v1.4.2 reported needing to refresh the page once before being able to add a disk to a VM.

Activity

  1. added
    kind/bugCategorizes issue or PR as related to a bug
    priority/backlogGeneral backlog priority. Lower than priority/important-longterm
    on Jun 3, 2026
  2. lexfrei commented on Jul 1, 2026

    @lexfrei
    ContributorAuthor

    Same underlying VM-disk-form issue as the v1.4.2 report in #2845. The relevant widget was rewritten on main (VMDiskWidget → DynamicOptionsWidget), so the original behaviour may already be fixed — this issue itself asks to confirm against current main. Marking needs-information pending a runtime repro.

  3. myasnikovdaniil commented on Aug 15, 2026

    @myasnikovdaniil
    Contributor

    Closing, does not reproduce on the current console. Checked in a browser against a live cluster: on a freshly loaded VM instance form the disks + add button adds exactly one row on the first click, and the disk name dropdown is populated straight away when the tenant has a VMDisk.

    What is almost certainly behind the original report is that the dropdown reads the tenant's own disks, so on a tenant with none it renders "No options available" and the form looks broken while behaving correctly. Reopen with the tenant's disk list if it shows up again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area/dashboardIssues or PRs related to the dashboard / UIkind/bugCategorizes issue or PR as related to a bugpriority/backlogGeneral backlog priority. Lower than priority/important-longtermtriage/needs-informationIndicates an issue needs more information in order to work on it

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions