Can't change VMhost overcommit back without a reload

Bug #1928792 reported by Alberto Donato
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Undecided
Unassigned
2.9
Won't Fix
Undecided
Unassigned
maas-ui
Fix Released
Unknown

Bug Description

From a VMhost (LXD or virsh) settings, if I change the CPU overcommit slider from 1 to something else, save, and then try to change it back, the save button gets disabled as soon as 1 is selected as value, so I can't save it again.

Reloading the page fixes the issue.

This seems to only happen if you change just the overcommit.

Note that the issue also happens with the memory slider, but for some reason it seems harder to reproduce (not all time times as the CPU one)

Tags: ui
Revision history for this message
Alberto Donato (ack) wrote :

I can reproduce this in 2.9 as well

Changed in maas:
milestone: none → 3.0.1
Changed in maas-ui:
importance: Undecided → Unknown
Bill Wear (billwear)
Changed in maas:
status: New → Triaged
Changed in maas-ui:
status: New → Fix Released
Changed in maas:
status: Triaged → Fix Committed
Changed in maas:
milestone: 3.0.1 → 3.2.0-beta1
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.