Bug 2104115

Summary:	RHV 4.5 cannot import VMs with cpu pinning
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Frank DeLorey <fdelorey>
Component:	ovirt-engine	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED ERRATA	QA Contact:	Qin Yuan <qiyuan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.5.0	CC:	dfodor, emarcus, ljelinko, lsurette, mavital, mzamazal, srevivo, ycui
Target Milestone:	ovirt-4.5.2
Target Release:	4.5.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.2	Doc Type:	Bug Fix
Doc Text:	Previously, when importing a virtual machine with manual CPU pinning (pinned to a dedicated host), the manual pinning string was cleared, but the CPU pinning policy was not set to NONE. As a result, importing failed. In this release, the CPU pinning policy is set to NONE if the CPU pinning string is cleared, and importing succeeds.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-09-08 11:28:53 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:

Comment 1 Lucia Jelinkova 2022-07-12 12:11:16 UTC

The key problem was that when importing a VM that has dedicated host and the host is not present in the cluster to which the VM is being imported, the dedicated host is cleared as well as the cpu pinning string. This leaves us with an empty cpu pinning string and MANUAL cpu pinning policy -> hence the failure on the database constraint.

Comment 4 Qin Yuan 2022-08-07 14:40:51 UTC

Verified with:
ovirt-engine-4.5.2.1-0.1.el8ev.noarch

Steps:
1. Prepare a storage domain containing a VM with following configurations:
   - pinned to a dedicated host which is not present in the target cluster
   - CPU pinning policy: Manual, CPU Pinning topology: 0#0
2. Import the storage domain to the target data center
3. Import the VM from the imported storage domain to the target cluster

Results:
1. The VM is imported successfully.
2. The VM is not pinned to any specific host.
3. The CPU pinning policy is changed to None, CPU Pinning topology is cleared.

Comment 5 meital avital 2022-08-08 19:42:52 UTC

Due to QE capacity, we are not going to cover this issue in our automation

Comment 7 Casper (RHV QE bot) 2022-09-04 20:05:08 UTC

This bug has low overall severity and is not going to be further verified by QE. If you believe special care is required, feel free to properly align relevant severity, flags and keywords to raise PM_Score or use one of the Bumps ('PrioBumpField', 'PrioBumpGSS', 'PrioBumpPM', 'PrioBumpQA') in Keywords to raise it's PM_Score above verification threashold (1000).

Comment 10 errata-xmlrpc 2022-09-08 11:28:53 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: RHV Manager (ovirt-engine) [ovirt-4.5.2] bug fix and security update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2022:6393