Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1288157

Summary:	[Cinder] Stateless VM with Cinder disk should be based on a cloned disk instead of a stateless snapshot.
Product:	[oVirt] ovirt-engine	Reporter:	Maor <mlipchuk>
Component:	BLL.Storage	Assignee:	Maor <mlipchuk>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Natalie Gavrielov <ngavrilo>
Severity:	high	Docs Contact:
Priority:	high
Version:	3.6.0	CC:	acanan, amureini, bugs, gklein, jbelka, mlipchuk, tnisan, ylavi
Target Milestone:	ovirt-3.6.2	Flags:	amureini: ovirt-3.6.z? ylavi: planning_ack+ amureini: devel_ack+ rule-engine: testing_ack?
Target Release:	3.6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-02-23 13:32:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1270725, 1305809
Bug Blocks:

Description Maor 2015-12-03 17:16:12 UTC

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:

Comment 1 Sandro Bonazzola 2015-12-23 13:44:27 UTC

oVirt 3.6.2 RC1 has been released for testing, moving to ON_QA

Comment 2 Tal Nisan 2016-01-04 15:59:53 UTC

Maor, do you think it might worth documenting it? If so please fill out the doc text

Comment 3 Jiri Belka 2016-01-20 13:03:06 UTC

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.

Comment 4 Maor 2016-01-20 16:57:45 UTC

Can u run a stateless VM with image disk? what the logs indicate what is the error?

Comment 5 Jiri Belka 2016-01-28 17:20:26 UTC

(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.

Comment 7 Natalie Gavrielov 2016-02-10 17:58:40 UTC

(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?

Comment 8 Maor 2016-02-11 14:42:51 UTC

(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...

Comment 10 Aharon Canan 2016-03-02 08:17:27 UTC

Removing needinfo, already closed