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

Bug 2074525

Summary: Misleading validation error (related to static&dynamic cpus conf) when nothing is changed in VM Edit window
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.5.0CC: ahadas, bugs, dfodor, lrotenbe, mzamazal
Target Milestone: ovirt-4.5.2Flags: pm-rhel: ovirt-4.5?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: 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-04-12 12:06:09 UTC 
Description of problem:Below there are two scenarios bringing the confusing validation error.

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

How reproducible: 100%

Steps to Reproduce Scenario1:
1. Configure VM with 4 CPUs, resize policy, pin to host. Run the VM.
2. Shuddown the VM.
3. Open Edit window, change nothing , click OK to close the dialog


Actual results:
  Error while executing action:
  golden_env_mixed_virtio_1:
  A NUMA node has an invalid CPU index: 45. Indexes must be between 0 and 3.

Expected results: Since nothing was changed for the VM , it must not bring misleading validation error

Scenario2:
1. The VM is created with 4 CPUs, 'Resize_and_pin_numa' policy.  DON'T pin to a host and Run_once VM on a specific host.
2. Try to pin such VM to a host in Edit/Host window.

actual result: Choosing the specific host changes immediately vNUMA nodes from0 to 2 which looks like a good thing to do. Then I get a message  saying that I need to restart the VM which is also ok. Then I get the message that actually means there is no way to perform the action I wanted:    "error while executing action  - A NUMA node has an invalid CPU index: 27. Indexes must be between 0 and 3."
Comment 1 Liran Rotenberg 2022-04-12 15:58:24 UTC 
The way to overcome this is - either use dynamic NUMA pinning (need to check if it's feasible) or cleanup the static NUMA configuration when the VM is down.
Comment 2 Polina 2022-04-24 08:58:20 UTC 
Another flow (from https://bugzilla.redhat.com/show_bug.cgi?id=1929260 ) must be tested in the scope of this bz, since this is the same cause root:
Run a VM set with resize_and_pin_numa on a host supporting NUMA . Reconfigure it to be High Performance type. Restart to apply the next configuration change.
Now we get an error "A NUMA node has an invalid CPU index: 45. Indexes must be between 0 and 3."
Comment 3 Polina 2022-05-03 11:30:41 UTC 
another scenario for this bug to test - try to rename resize_and_pin VM pinned to host - brings error "A NUMA node has an invalid CPU index: 27. Indexes must be between 0 and 1."
Comment 4 Polina 2022-07-26 09:30:36 UTC 
verified on ovirt-engine-4.5.2-0.3.el8ev.noarch for 4 scenarios described in the bz .
Comment 5 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.