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

Bug 1507350

Summary:	Windows VM does a mini-setup when pool created with latest subversion template
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Pawan kumar Vilayatkar <pvilayat>
Component:	ovirt-web-ui	Assignee:	Marek Libra <mlibra>
Status:	CLOSED DUPLICATE	QA Contact:	Pavel Stehlik <pstehlik>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.2	CC:	lsvaty, michal.skrivanek, mkalinin, pvilayat, tjelinek
Target Milestone:	---	Flags:	lsvaty: testing_plan_complete-
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 23:43:11 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 Pawan kumar Vilayatkar 2017-10-30 01:02:28 UTC

Description of problem:

1. Created a pool over a latest subversion template.
2. Create a new version of the pool
3. Power down vm in the pool (40ADMIN-1)
4. Re-created the vm
5. The next powerdown cycle the vm does a mini-setup again, seems it's not persistent after the first subversion update. While on creation was good.



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


How reproducible:

The issue is re-producible . 



Steps to Reproduce:
1. Create a template A

2. Create a pool POOL_A over latest (A)

3. Power up VM

4. Power down

5. Power up stateless

6. Create a subtemplate

7. powerdown VM. In this moment, rhevm delete old mv and create again the same vm with reference to the new subtemplate, and start the mini-setup



Actual results:

Starting VM stateless then creating subtemplate and after power down and power
up VM does a mini-setup


Expected results:

The VM should do perform mini-setup



Additional info:

For customer the description of the behaviour, is not the expected for us, and from our point of view it does not make sense for a massive pool installation where at least for windows vms is needed the mini-setup.

Comment 1 Michal Skrivanek 2017-10-30 06:49:07 UTC

Thos sounds like a correct behavior. Why is it surprising? "Latest" template version keeps VM updated to the latest version and if that is different from the previous one it will do whatever is in the new template. Does docs suggest a different behavior? What are the exact expectations?

Comment 2 Tomas Jelinek 2017-11-23 09:08:32 UTC

Any news?

Comment 3 Marina Kalinin 2017-11-29 17:19:04 UTC

I am not sure, but seems like this bug should be close as duplicate of this rfe: 
https://bugzilla.redhat.com/show_bug.cgi?id=1457549
We are checking with the customer about the exact use case.

Comment 4 Yaniv Kaul 2017-12-18 11:26:00 UTC

(In reply to Marina from comment #3)
> I am not sure, but seems like this bug should be close as duplicate of this
> rfe: 
> https://bugzilla.redhat.com/show_bug.cgi?id=1457549
> We are checking with the customer about the exact use case.

Any updates?

Comment 5 Marina Kalinin 2017-12-20 23:43:11 UTC

Customer confirmed that this rfe bz#1457549 is exactly his use case. Closing as duplicate.

*** This bug has been marked as a duplicate of bug 1457549 ***