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

Bug 1930298

Summary: 'NUMA Node Count' number is not set if at the same editing the user sets vcpu pinning.
Product: [oVirt] ovirt-engine Reporter: Polina <pagranat>
Component: Frontend.WebAdminAssignee: Liran Rotenberg <lrotenbe>
Status: CLOSED CURRENTRELEASE QA Contact: Polina <pagranat>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.4.5CC: ahadas, bugs
Target Milestone: ovirt-4.4.7Keywords: ZStream
Target Release: 4.4.7.1Flags: pm-rhel: ovirt-4.4+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ovirt-engine-4.4.7.1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-07-06 07:28:25 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 2021-02-18 16:38:08 UTC 
Description of problem:'NUMA Node Count' number is not set when editing includes vcpu pinning


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

How reproducible:100%


Steps to Reproduce:
0. Setup must have host supporting NUMA arch
1. Create a VM on the base of infra template and open Edit window.
2. System tab - configure 8 CPUs
3. Host tab - pin to the numa host and set 1 'NUMA Node Count'.
4. Resource Allocation tab - enter some vcpu pinning string , like 0#0_1#1
5. OK in the dialog and re-open 

Actual results: 'NUMA Node Count' = 0


Expected results:'NUMA Node Count' = 1


Additional info: the bug doesn't happen if we don't configure vcpu pinning
Comment 1 Polina 2021-06-21 10:23:04 UTC 
verified on ovirt-engine-4.4.7.4-0.9.el8ev.noarch
Comment 2 Sandro Bonazzola 2021-07-06 07:28:25 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.