Bug 1929730

Summary: Fails to update vNUMA nodes from number to 0 for running VM (next configuration run).
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: BLL.VirtAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.4.4.5CC: ahadas, bugs
Target Milestone: ovirt-4.4.7Keywords: ZStream
Target Release: 4.4.7Flags: pm-rhel: ovirt-4.4+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-06 07:28:18 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:
Attachments:
Description Flags
engine.log none

Description Polina 2021-02-17 14:11:44 UTC
Created attachment 1757569 [details]
engine.log

Description of problem: For a running VM the VNUMa nodes number could be updated from number to number but not to the 0.


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

How reproducible: 1. Configure VM with 2 numa nodes , start , 
2. For the running VM change numa nodes to 0 - 'Changes that require Virtual Machine restart:' window appears which is right , but we can already see at this step that the yellow triangle icon of the next configuration doesn't appear.
3. Restart VM - still see 2. 100%


Steps to Reproduce:
1. Configure VM with 2 numa nodes , start , 
2. For the running VM change numa nodes to 0 - 'Changes that require Virtual Machine restart:' window appears which is right , but we can already see at this step that the yellow triangle icon of the next configuration doesn't appear.
3. Restart VM - still see 2. 

Actual results:
After restart we still see the previous number of vNUMA nodes

Expected results:0 for vNUMA nodes


Additional info:

Comment 1 Polina 2021-06-03 10:09:25 UTC
verified on ovirt-engine-4.4.7-0.23.el8ev.noarch

Comment 2 Sandro Bonazzola 2021-07-06 07:28:18 UTC
This bugzilla is included in oVirt 4.4.7 release, published on July 6th 2021.

Since the problem described in this bug report should be resolved in oVirt 4.4.7 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.