Hi list, When a user powers down a VM from within the VM operating system (poweroff), a "moved from 'Up' --> 'Down'" message is written to engine.log, and a EVENT_ID: VM_DOWN is created
-- 2019-05-08 20:53:03,495+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'Up' --> 'Down' 2019-05-08 20:53:03,550+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-3) [] EVENT_ID: VM_DOWN(61), VM vmname1 is down. Exit message: User shut down from within the guest -- When a user starts a VM from the webadmin, a "moved from 'WaitForLaunch' --> 'PoweringUp'" and "'PoweringUp' --> 'Up'" is written to engine.log, and the events EVENT_ID: USER_STARTED_VM and EVENT_ID: USER_RUN_VM is created. -- 2019-05-08 20:53:20,976+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (EE-ManagedThreadFactory-engine-Thread-1388598) [xxxxxxxx-da2d-452d-a604-xxxxxxxxxxxx] EVENT_ID: USER_STARTED_VM(153), VM vmname1 was started by adminuser@ipadomain (Host: hypervisor1). 2019-05-08 20:53:24,091+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'WaitForLaunch' --> 'PoweringUp' 2019-05-08 20:53:45,140+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-3) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'PoweringUp' --> 'Up' 2019-05-08 20:53:45,238+02 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-3) [] EVENT_ID: USER_RUN_VM(32), VM vmname1 started on Host hypervisor1 -- However when a user reboots a VM from within the VM operating system, the messages "moved from 'Up' --> 'RebootInProgress'" and "moved from 'RebootInProgress' --> 'Up'" is written to the engine.log, but no EVENT_ID is generated. -- -- 2019-05-08 20:52:27,367+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'Up' --> 'RebootInProgress' 2019-05-08 20:52:49,926+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1) [] VM 'xxxxxxxx-3966-4da2-a505-xxxxxxxxxxxx'(vmname1) moved from 'RebootInProgress' --> 'Up' -- So systems like CloudForms/ManageIQ which reads the manager event log via the manager REST API is not notified when a VM is rebooted, and is therefore unable to perform any EmsEvent when the VM reboots. Why is there no EVENT_ID generated when a VM reboots? Is it possible to enable EVENT_ID's to be created for VM reboot events? Regards, Siggi _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/IHW2RQT3RRPV7IJJZP4EQCIGF5TZYS6Z/
