Problem Description : With OSP16 VM getting crashed all of suddenly, it is changing from ACTIVE from SHUTOFF state, when used with Alma Linux 8.6/8.7
In libvirt logs :
2023-05-03 13:33:56.436+0000: shutting down, reason=crashed
2023-05-03 06:33:55.338 8 DEBUG nova.compute.manager [req-01acf353-5fee-4171-accf-ac3daa54d197 - - - - -] Starting heal instance info cache _heal_instance_info_cache /usr/lib/python3.6/site-packages/nova/compute/manager.py:8201
2023-05-03 06:34:11.529 8 DEBUG nova.virt.driver [-] Emitting event <LifecycleEvent: 1683120836.527273, 0d994c12-404b-40c5-9cb0-c9f31b12bcbb => Stopped> emit_event /usr/lib/python3.6/site-packages/nova/virt/driver.py:1733
2023-05-03 06:34:11.530 8 INFO nova.compute.manager [-] [instance: 0d994c12-404b-40c5-9cb0-c9f31b12bcbb] VM Stopped (Lifecycle Event)
2023-05-03 06:34:11.574 8 DEBUG nova.compute.manager [req-d3022c95-fee0-4e3f-92d7-9d0341231fbe - - - - -] [instance: 0d994c12-404b-40c5-9cb0-c9f31b12bcbb] Checking state _get_power_state /usr/lib/python3.6/site-packages/nova/compute/manager.py:1507
2023-05-03 06:34:11.576 8 DEBUG nova.compute.manager [req-d3022c95-fee0-4e3f-92d7-9d0341231fbe - - - - -] [instance: 0d994c12-404b-40c5-9cb0-c9f31b12bcbb] Synchronizing instance power state after lifecycle event “Stopped”; current vm_state: active, current task_state: None, current DB power_state: 1, VM power_state: 4 handle_lifecycle_event /usr/lib/python3.6/site-packages/nova/compute/manager.py:1252
2023-05-03 06:34:11.625 8 INFO nova.compute.manager [req-d3022c95-fee0-4e3f-92d7-9d0341231fbe - - - - -] [instance: 0d994c12-404b-40c5-9cb0-c9f31b12bcbb] During _sync_instance_power_state the DB power_state (1) does not match the vm_power_state from the hypervisor (4). Updating power_state in the DB to match the hypervisor.
Please let me know how I can atatch logs from compute/controllers, as I don’'t see such provision. Kindly help .