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

Bug 1583641

Summary:	Sysprep payload not created on definitive hypervisor
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Kevin van Hoorn <kevin.van.hoorn>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:	meital avital <mavital>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.1.10	CC:	lsurette, ptoscano, Rhev-m-bugs, srevivo, ykaul
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-01-03 12:49:39 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 Kevin van Hoorn 2018-05-29 12:14:40 UTC

Description of problem:
On a cluster where the CPU Type is set to Intel SandyBridge and 40 hosts, there are 5 hosts with a CPU Type of SandyBridge, the rest supports Broadwell.

The Pool is made with a Windows 7 template wich requires Broadwell. This meanse the pool can run on 35 of the 40 hosts. 

When a new VM spins up on one of the 5 incompatible hosts, it creates the payload image (with sysprep) on the incompatible host and then thrown an error and move to a compatible host. The payload though, is not moved to the new host, hence a boot with sysprep is not possible. The payload on the incompatible host is removed.

Version-Release number of selected component (if applicable):
vdsm: 4.19.50-1
RHEV Manager Version: 4.1.10.3-0.1.el7

How reproducible:
Likely reproducible

Steps to Reproduce:
1. Create cluster with 1 Broadwell and 1 SandyBridge 
2. Create Windows Pool with size of 3 minimum with Broadwell requirement
3. Boot up machines in pool.

Actual results:
Machine that wanted to boot on legacy host is not fully installed due to missing payload

Expected results:
Machine boots as expected (sysprep payload is moved or recreated on definitive host).

Additional info:

Comment 1 Richard W.M. Jones 2018-05-29 12:36:10 UTC

We think this bug is probably assigned to the wrong component.
I'm not sure what it's talking about.  I'm reassigning it to
RHEV-M / ovirt-engine.

Comment 3 Ryan Barry 2019-01-03 12:49:39 UTC

This will not be addressed in a reasonable timeframe. Please re-open if it's still important.