Description of problem:
No EVENT_ID is generated in /var/log/ovirt-engine/engine.log when VM is rebooted from OS level itself.
Version-Release number of selected component (if applicable):
Red Hat Virtualization 4.2
Steps to Reproduce:
1. Reboot the VM from OS level itself
2. Check /var/log/ovirt-engine/engine.log for reboot messages for VM.
Only VM rebooting messages are logged, but no EVENT_ID generated.
EVENT_ID should be logged. So that systems like Cloudforms/ManageIQ can read the event log via rhvm rest api and get notified if the VM is rebooted.
-- Following messages are logged in /var/log/ovirt-engine/engine.log
2019-05-08 20:52:27,367+02 INFO [org.ovirt.engine.core.vdsbroker.monitoring.VmAnalyzer] (ForkJoinPool-1-worker-1)  VM 'xxxxxxxx-xxxxxxxx-xxxxxxxxxxxx'(TestVM) 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-xxxxxxxx-xxxxxxxxxxxx'(TestVM) moved from 'RebootInProgress' --> 'Up'
Reboots are expected to be initiated from RHVM or the API.
For guest-level uptime monitoring, why not use guest agent data to track it?
it's detected properly as per the engine.log message, just the audit log event is not fired. Should be as simple as reusing the AuditLogType.USER_REBOOT_VM when Up->RebootInProgress
Given that the event is already picked up by the manager, and that all that needs to be done to fix this issue is to add the existing audit log type AuditLogType.USER_REBOOT_VM to this event. Why is this request taking so long time to implement?
verified on http://bob-dr.lab.eng.brq.redhat.com/builds/4.4/rhv-4.4.0-31
2020-04-22 21:33:28,952+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ForkJoinPool-1-worker-25)  EVENT_ID: USER_REBOOT_VM(157), VM golden_env_mixed_virtio_0 is rebooting. Rebooted by: Guest OS
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.