Description of problem: A stateless VM with image disk is being used by running the VM on the snapshot's volume. Cinder disk behaves differently by that, that the Cinder's snapshot is not a volume which the VM can run on it. Instead a cloned volume should be created on the base volume and when the VM gets shutdown the cloned volume should get removed. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1.Start a stateless VM with Cinder disk 2.Stop the VM 3.The stateless snapshot gets removed with Actual results: Expected results: Additional info:
oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA
Maor, do you think it might worth documenting it? If so please fill out the doc text
I can't run stateless VM which has a disk on cinder. Run is initialized, new disk appears in cinder but later on the VM is still down and there's no error. rhevm-3.6.2.5-0.1.el6.noarch Second run of the same VM causes a popup with: Cannot run VM. Related operation is currently in progress. Please try again later.
Can u run a stateless VM with image disk? what the logs indicate what is the error?
(In reply to Maor from comment #4) > Can u run a stateless VM with image disk? what the logs indicate what is the > error? Yes I can run a stateless VM with "normal" (nfs-based) disk. I cannot do that with cinder disk.
(In reply to Jiri Belka from comment #3) > I can't run stateless VM which has a disk on cinder. Run is initialized, new > disk appears in cinder but later on the VM is still down and there's no > error. > > rhevm-3.6.2.5-0.1.el6.noarch > > Second run of the same VM causes a popup with: > > Cannot run VM. Related operation is currently in progress. Please try again > later. I'm getting the same result.. meaning this test is blocked by this bug. Maor, Was there an issue opened about stateless vm cannot be started? Aharon, I tested this issue partially (using 3.6.3), the following way: 1. Created a vm with nfs disk as bootable disk. 2. Attach a cinder disk. 3. Install OS, write a file. 3. Run once as stateless. 4. Write another file. The run once (third step) creates a cinder volume, and when shutting down the vm, it's removed. (When running the vm again, not stateless mode file from step 4 is gone - as expected). Should I move this issue to verified, or should we wait until the above is fixed?
(In reply to Natalie Gavrielov from comment #7) > (In reply to Jiri Belka from comment #3) > > I can't run stateless VM which has a disk on cinder. Run is initialized, new > > disk appears in cinder but later on the VM is still down and there's no > > error. > > > > rhevm-3.6.2.5-0.1.el6.noarch > > > > Second run of the same VM causes a popup with: > > > > Cannot run VM. Related operation is currently in progress. Please try again > > later. > > I'm getting the same result.. meaning this test is blocked by this bug. > > Maor, > > Was there an issue opened about stateless vm cannot be started? There is an issue which the stateless snapshot is staying in locked status forever (BZ1305809) and the VM cannot be started. > > Aharon, > > I tested this issue partially (using 3.6.3), the following way: > 1. Created a vm with nfs disk as bootable disk. > 2. Attach a cinder disk. > 3. Install OS, write a file. > 3. Run once as stateless. > 4. Write another file. > > The run once (third step) creates a cinder volume, and when shutting down > the vm, it's removed. > (When running the vm again, not stateless mode file from step 4 is gone - as > expected). > > Should I move this issue to verified, or should we wait until the above is > fixed? I suggest that every scenario related to Cinder and stateless mode will wait for BZ1305809 fix, since the fix for it might impact this scenario also, though it is up to the QE to decide...
Removing needinfo, already closed