Bug 1421420
Summary: | Update VM 'Console->Advanced Parameters->Disable strict user checking' will initiate 'VM NUMA add' audit message | ||
---|---|---|---|
Product: | [oVirt] ovirt-engine | Reporter: | Artyom <alukiano> |
Component: | Backend.Core | Assignee: | Nobody <nobody> |
Status: | CLOSED DUPLICATE | QA Contact: | meital avital <mavital> |
Severity: | low | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1.0.4 | CC: | akrejcir, alukiano, bugs, dfediuck, msivak |
Target Milestone: | --- | ||
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: | 2017-03-01 11:32:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | SLA | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1291064 | ||
Bug Blocks: |
Description
Artyom
2017-02-12 08:37:38 UTC
Dup of bug 1291064 ? Do not think so, the https://bugzilla.redhat.com/show_bug.cgi?id=1291064 connect to the fact that the engine does not update automatically NUMA node memory and CPU in case if I update the VM memory or CPU. In this bug, I talk about some small issue with audit messages(I believe it connect to the fact that we have 'strict' NUMA mode, so when I update the option 'Disable strict user checking', somewhere in the code we parse it as NUMA mode) It may be just a side effect and not a bug. We now verify NUMA updates on every edit VM, which outputs this message when a numa update indeed happens. Martin, can you please verify? This is probably unwanted side effect of the fix for Bug 1291064. Now, SetVmNumaNodes command is called every time a VM is edited, which is unnecessary. The fix will be part of Bug 1291064. *** This bug has been marked as a duplicate of bug 1291064 *** |