Bug 1292086

Summary:	[sysprep] RunOnce: Sysprep floppy payload attached to normal VM regardless of its settings enabling
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	ovirt-engine	Assignee:	Nobody <nobody>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.5.0	CC:	bmcclain, ecohen, gklein, gscott, istein, juan.hernandez, lpeer, lsurette, mavital, mgoldboi, michal.skrivanek, nsimsolo, ofrenkel, rbalakri, rhev-integ, Rhev-m-bugs, shavivi, sshnaidm, yeylon
Target Milestone:	ovirt-3.5.7	Keywords:	Regression, Reopened, ZStream
Target Release:	3.5.7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Sysprep floppy was attached by default on every new Windows VM regardless if the user defined Sysprep in the initialization section Consequence: Unnecessary floppy with Sysprep information was attach to a first run of a Windows VM. Result: Sysprep is attached to Windows VM only in the first run and only if the user explicitly enabled initialization section.	Story Points:	---
Clone Of:	1240900	Environment:
Last Closed:	2016-01-18 13:35:46 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Virt	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1190663, 1240900
Bug Blocks:	1242426, 1242428

Description Michal Skrivanek 2015-12-16 12:41:34 UTC

+++ This bug was initially created as a clone of Bug #1240900 +++

+++ This bug is a RHEV-M zstream clone. The original bug is: +++
+++   https://bugzilla.redhat.com/show_bug.cgi?id=1190663. +++
+++ Requested by "mskrivan" +++
======================================================================

Comment 1 Michal Skrivanek 2015-12-16 12:42:48 UTC

see https://bugzilla.redhat.com/show_bug.cgi?id=1240900#c5 onwards

Comment 3 Nisim Simsolo 2015-12-17 14:07:49 UTC

Verified:
rhevm-3.6.1.3-0.1.el6
libvirt-client-1.2.8-16.el7_1.4.x86_64
sanlock-3.2.2-2.el7.x86_64
qemu-kvm-rhev-2.1.2-23.el7_1.11.x86_64
vdsm-4.16.31-1.el7ev.x86_64

Verification scenario:
1. Create VM and seal it.
2. Verify sysprep is disabled on the VM, From user portal/extended, add disk to VM and run it.
3. Verify sysprep payload is not attached to VM.
4. Power off VM and run it again.
5. Verify sysprer payload is not attached to VM.

Comment 4 Michal Skrivanek 2016-01-04 15:52:19 UTC

this is a 3.5 bug/clone, was it verified there?

Comment 5 Eyal Edri 2016-01-18 13:35:46 UTC

3.5.7 was released.

Comment 6 Nisim Simsolo 2016-02-21 07:21:54 UTC

Yes: https://bugzilla.redhat.com/show_bug.cgi?id=1240900#c2