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

Bug 2111088

Summary:	hotplug CPU error has been brought upon dedicated VM shutting down
Product:	[oVirt] ovirt-engine	Reporter:	Polina <pagranat>
Component:	BLL.Virt	Assignee:	Lucia Jelinkova <ljelinko>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Nikolai Sednev <nsednev>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.5.2	CC:	bugs, mavital, mzamazal, sbonazzo
Target Milestone:	ovirt-4.5.2	Keywords:	PrioBumpQA, Triaged, ZStream
Target Release:	4.5.2	Flags:	nsednev: needinfo- sbonazzo: ovirt-4.5+
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ovirt-engine-4.5.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-30 08:47:42 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 Polina 2022-07-26 13:27:25 UTC

Description of problem:
I have a running VM with 3 CPUs and dedicated policy. I want to reconfigure it and shut down: change the CPU to 1 and policy to 'none'. I didn't intend to hotplug anything. Upon shutting down I get error
"Hot plugging a CPU is not supported with the CPU pinning policy DEDICATED." .

Version-Release number of selected component (if applicable):
ovirt-engine-4.5.2-0.3.el8ev.noarch

How reproducible:100%


Steps to Reproduce:
1. Run VM configured with 3 CPUs and dedicated policy.
2. Change configuration - CPU to 1 , dedicated policy to 'none' and try to shutdown. 

Actual results:
Shutdown fails error
"Hot plugging a CPU is not supported with the CPU pinning policy DEDICATED." .

Expected results: the VM must shut down .


Additional info:

Comment 1 Polina 2022-08-02 18:54:09 UTC

the bug is on_qa , but still happens on the last available build . tested on ovirt-engine-4.5.2-0.3.el8ev.noarch

Comment 3 Nikolai Sednev 2022-08-15 12:33:12 UTC

The original error has been fixed on these components:
ovirt-engine-setup-4.5.2.2-0.1.el8ev.noarch
ovirt-hosted-engine-ha-2.5.0-1.el8ev.noarch
ovirt-hosted-engine-setup-2.6.5-1.1.el8ev.noarch
Linux 4.18.0-372.19.1.el8_6.x86_64 #1 SMP Mon Jul 18 11:14:02 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux

Comment 4 Sandro Bonazzola 2022-08-30 08:47:42 UTC

This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022.
Since the problem described in this bug report should be resolved in oVirt 4.5.2 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.