Red Hat Bugzilla – Bug 1305945
All fields in edit VM disk dialog are wrongly editable
Last modified: 2016-03-10 07:47:46 EST
Created attachment 1122445 [details]
ovirt / vdsm logs
Description of problem:
Select VM disk that has Allocation Policy of thin provision.
Attempt to set to preallocated, all seems successful via the UI and Events panel. Actual change was not successful, and VM disk remains as thin.
Engine log reports ACTION_TYPE_FAILED_VM_IS_LOCKED
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Select Disk, and Press Edit
2.Set Allocation Policy to PreAllocated from Thin
4.Event log shows VM X disk was updated successfully by admin
Editing the disk via UI after attempting to set to preallocated show it remains on thin. The ovirt log shows the update disk failed: ACTION_TYPE_FAILED_VM_IS_LOCKED.
Allocation policy changed as drop down indicates, or warning that the disk update command failed.
Attempted with VMs that were on, or off.
Found in 3.6.2, also reproduced in separate enviroment of 3.6.3
The bug is not the fact that the allocation policy cannot be changed since we never supported a change in the allocation policy, the actual bug resides in the fact that fields that cannot be updated appear as changeable (Allocation Policy, Size and more).
Investigating now, but this is the actual regression here.
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.
The following fields are greyed out in edit disk prompt: