Looks like a bug...
Under the engine log I can see:
2017-02-12 03:18:03,160-05 INFO
[org.ovirt.engine.core.bll.UpdateVmCommand] (default task-22)
[43c019b6-06b8-4c2f-bb2b-0639ebd17df9] Running command: Upd
ateVmCommand internal: false. Entities affected : ID:
5df59ddd-a70a-405e-b528-f02bdcf0d3c9 Type: VMAction group
EDIT_VM_PROPERTIES with role type USER
2017-02-12 03:18:03,171-05 INFO
[org.ovirt.engine.core.bll.numa.vm.SetVmNumaNodesCommand] (default
task-22) [6bf7ace6] Running command: SetVmNumaNodesCom
mand internal: true.
2017-02-12 03:18:03,180-05 INFO
[org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector]
(default task-22) [6bf7ace6] EVENT_ID: NUMA_ADD_VM
_NUMA_NODE_SUCCESS(1,300), Correlation ID: 6bf7ace6, Call Stack: null,
Custom Event ID: -1, Message: Add VM NUMA node successfully.
But it least it does not change VM NUMA mode, will open the bug for this
issue.
Thanks
On Sat, Feb 11, 2017 at 5:43 PM, Gianluca Cecchi
wrote:
> Hello,
> yesterday I saw this message 3 times
>
> Add VM NUMA node successfully.
>
> and it seems to me that it was at the same time when I edited some VMs and
> in
> Console --> Advance parameters
> I set "disable strict user checking"
> Are they indeed related? What is the relation with NUMA?
>
> Thanks,
> Gianluca
>
>
>
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
>
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
