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

Bug 1973270

Summary:	[RFE] Make VM sealing configurable
Product:	[oVirt] ovirt-engine	Reporter:	Arik <ahadas>
Component:	Frontend.WebAdmin	Assignee:	Shmuel Melamud <smelamud>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nisim Simsolo <nsimsolo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.4.7	CC:	bugs, nsimsolo
Target Milestone:	ovirt-4.4.8	Keywords:	FutureFeature, ZStream
Target Release:	4.4.8.2	Flags:	ahadas: ovirt-4.4? pm-rhel: planning_ack? pm-rhel: devel_ack? pm-rhel: testing_ack+
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.4.8.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1981100 2054681 (view as bug list)		Environment:
Last Closed:	2021-08-19 06:23: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:
Bug Depends On:
Bug Blocks:	1981100, 2054681

Description Arik 2021-06-17 14:10:30 UTC

In bz 1887434 we made the engine call sysprep when creating the VM from a sealed template, in addition to when creating the template for VMs that are not part of pools.

The next step would be to make it configurable.
That is, to let the user choose whether or not to seal the created VM and keeping the existing behaviour as default.

Comment 1 Nisim Simsolo 2021-08-16 13:25:20 UTC

Verified:
ovirt-engine-4.4.8.4-0.7.el8ev
vdsm-4.40.80.5-1.el8ev.x86_64
libvirt-daemon-7.0.0-14.3.module+el8.4.0+11878+84e54169.x86_64
qemu-kvm-5.2.0-16.module+el8.4.0+12191+622ad3bb.5.x86_64

Verification scenario:
Polarion test case added to bug links

Comment 2 Sandro Bonazzola 2021-08-19 06:23:11 UTC

This bugzilla is included in oVirt 4.4.8 release, published on August 19th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.8 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.