You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
VM create form: cannot add a disk until the page is refreshed once #3109
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:
"prevent stale RJSF state from overriding user input"
"stop VMDiskWidget dropping the selected disk on submit" (Release 0.1.0 #25)
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
Fresh-navigate to the VM create form on current main.
Without refreshing, try to add a disk.
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.
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.
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.
Activity
lexfrei commentedon Jul 1, 2026
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.
myasnikovdaniil commentedon Aug 15, 2026
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
+ addbutton 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.