Created attachment 489048 [details] screen shot and log Description of problem: when creating a new VM with 2 disks, and creating both disks with guide me, if the second disk is created while first disk is till created it will result in error message that Disk cannot be created because the VM is not down (see screen shot) Version-Release number of selected component (if applicable): ic107 How reproducible: 100% Steps to Reproduce: 1. create VM 2. create disk using the guide me 3. create a second disk using the guide me Actual results: Error message will appear on the second disk that disk cannot be created because the VM is not down Expected results: - use async tasks if possible - allow the creating only when first disk is finished - error message should also be changed since VM is down Additional info:screen shot + backend log
- changed the subject (the message is not "VM is running" but "VM is not down") - the VM *is* not down - it is in "Image Locked" state because it is in the middle of the creation of the first disk. This is a problematic situation, since the VM can change its status while the guide-me is open, and currently the guide-me dialog is not "sensitive" for status changes. I am marking this as rhevm_future - we need to re-think about all guide-me's, not only the VM one, and possibly other dialogs as well.
From Bug 722931, comment #1 (by me), regarding Data-Center Guide Me dialog: There are a few issues here; the most painful one is the "Configure Storage" button that remains grayed out; I assume that it remains grayed out since the "Guide me" dialog is not "sensitive" for status changes: after finishing adding a new Host to the data-center, the Host probably hasn't reached the "Up" status yet, which causes the "Configure Storage" button to remain in a gray-out mode. After a few seconds, the Host probably moves to "Up" state, and you would expect the "Configure Storage" button to become enabled, only (as I stated earlier) the dialog is currently not "sensitive" to status changes.
Removing "Regression" keyword (behavior is the same since 2.2)
Why not to disable the create disk button while the vm is not down?
wouldn't this be allowed for hot plugging a disk?
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.