Bug 1072375

Summary:	VM doesn't start when dirty stateless snapshot exists
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	General	Assignee:	Arik <ahadas>
Status:	CLOSED WONTFIX	QA Contact:	sefi litmanovich <slitmano>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	---	CC:	ahadas, bugs, gklein, istein, michal.skrivanek, rbalakri, rgolan, tspeetje, yeylon
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-10 10:48:17 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Arik 2014-03-04 13:22:20 UTC

Description of problem:
If for some reason the stateless snapshot was not removed for stateless VM from its last run, on next run the VM won't start - the user gets an error that stateless snapshot exists and it is going to be removed, and only on next run the VM will actually start. It is a bad user experience.

Version-Release number of selected component (if applicable):


How reproducible:
100%


Steps to Reproduce:
1. Run stateless VM
2. Stop the VM while the SPM is down
3. Run VM

Actual results:
The VM doesn't start. We're producing an error for failing to run the VM because stateless snapshot exists and then remove the stateless snapshot.

Expected results:
The stateless snapshot should be removed and then we should try to run the VM.

Additional info:
It seems that it wasn't possible before but now that we can execute command sequentially, it should be possible.

Comment 1 Tim Speetjens 2014-06-06 09:47:06 UTC

Arik,
Do we have any relevant messages in engine.log or vdsm.log to positively identify this problem?

Thanks
Tim

Comment 2 Arik 2014-06-08 15:13:38 UTC

Tim, there is such a message in the engine log.
In 3.4 and above: VM {0} ({1}) already contains stateless snapshot, removing it
In 3.3 and below: RunVmAsStateless - {0} - found stateless snapshots for this vm  - skipped creating snapshots

Comment 3 Michal Skrivanek 2014-08-22 14:26:05 UTC

this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know

Comment 4 Ilanit Stein 2015-08-20 13:44:41 UTC

Can you please elaborate on steps to reproduce 
'2. Stop the VM while the SPM is down':
What are the exact steps here?

Thanks,
Ilanit.

Comment 5 Sandro Bonazzola 2015-09-04 08:59:57 UTC

This is an automated message.
This Bugzilla report has been opened on a version which is not maintained anymore.
Please check if this bug is still relevant in oVirt 3.5.4.
If it's not relevant anymore, please close it (you may use EOL or CURRENT RELEASE resolution)
If it's an RFE please update the version to 4.0 if still relevant.

Comment 6 Michal Skrivanek 2015-09-23 07:31:39 UTC

This bug didn't fit the 3.6 release in time and has been postponed to the next version. Please escalate if you think it should block 3.6

Comment 7 Red Hat Bugzilla Rules Engine 2015-10-19 10:59:53 UTC

Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 8 Yaniv Kaul 2016-03-10 10:48:17 UTC

Closing old tickets, in medium/low severity. If you believe it should be re-opened, please do so and add justification.