Comment 0 for bug 1975810

Openstack notification for 'STOPPED' event and cluster status 'OFFLINE' triggers a host evacuation, althou the host is up and the nova-compute service is running, even though the masakari sets the hypervisor disabled for nova:

| 107 | nova-compute | compute-server-4 | AZ3 | disabled | up | 2022-05-26T09:27:40.000000 |

notification:
| 9971bb37-7e97-4781-af4e-690ad5853caa | 2022-05-24T13:44:55.000000 | failed | COMPUTE_HOST | f975d04f-a345-4ea0-994b-5f014fbd146b | {'event': 'STOPPED', 'cluster_status': 'OFFLINE', 'host_status': 'NORMAL'} |

The results as usual is evacuation will fail as the nova-compute service MUST be down for an evacuation to happen, not only the disabling of the compute service

workflow details: https://pastebin.ubuntu.com/p/X9pTjsD6kJ/

Charmed deployment of masakari rev 67, on bionic/ussuri with the following packages:

ii masakari-api 9.0.0-0ubuntu0.20.04.3~cloud0 all Virtual Machine High Availability (VMHA) for OpenStack - API Server
ii masakari-common 9.0.0-0ubuntu0.20.04.3~cloud0 all Virtual Machine High Availability (VMHA) for OpenStack - Common Files
ii masakari-engine 9.0.0-0ubuntu0.20.04.3~cloud0 all Virtual Machine High Availability (VMHA) for OpenStack - Engine
ii python3-masakari 9.0.0-0ubuntu0.20.04.3~cloud0 all Virtual Machine High Availability (VMHA) for OpenStack - Python 3