Description of problem: Trying to attach a disk to vm that is in 'Reboot in progress' state ends up with <fault></fault> object: <fault> <reason>Operation Failed</reason> <detail>[Cannot attach Virtual Machine Disk because it is in Reboot in Progress status.]</detail> </fault>. The details is confusing: from the details it appears that the disk is in 'Reboot in Progress' status, which is incorrect. Version-Release number of selected component (if applicable): rhevm-3.4.0-0.13.beta3.el6ev.noarch How reproducible: 100% Steps to Reproduce: 1. attach disk to vm that is in reboot status 2. 3. Actual results: <fault> <reason>Operation Failed</reason> <detail>[Cannot attach Virtual Machine Disk because it is in Reboot in Progress status.]</detail> </fault>. Expected results: <fault> <reason>Operation Failed</reason> <detail>[Cannot attach Disk to Virtual Machine because it is in Reboot in Progress status.]</detail> </fault>. Additional info:
Jodi, can you please approve the message in the expected result above (or alternatively, suggest a better one? `-)). Thanks!
[Cannot attach Disk to Virtual Machine because its status is still Reboot in Progress] Hope that makes it clearer :)
Verified - ovirt-engine-3.5.0-0.0.master.20140605145557.git3ddd2de.el6.noarch As expected: <fault> <reason>Operation Failed</reason> <detail> [Cannot attach Virtual Machine Disk because the VM is in Reboot in Progress status.] </detail> </fault>
RHEV-M 3.5.0 has been released, closing this bug.