process-monitor: updating nova venv results in downtime
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| masakari-monitors |
Undecided
|
Unassigned |
Bug Description
Today we ran openstack-ansible after switching our openstack-ansible from stable/stein-Branch to 19.0.0-Tag. Doing so, we called setup-openstack
Analyzing this state we found in /var/log/
Aug 7 12:07:56 host1 systemd[1]: Stopping nova-compute service...
Aug 7 12:07:57 host1 systemd[1]: Stopped nova-compute service.
Aug 7 12:07:57 host1 systemd[1]: nova-compute.
Aug 7 12:07:57 host1 systemd[1]: Started nova-compute service.
Aug 7 12:07:59 host1 systemd[1]: Stopping nova-compute service...
Aug 7 12:07:59 host1 systemd[1]: Stopped nova-compute service.
Aug 7 12:07:59 host1 systemd[1]: nova-compute.
Aug 7 12:07:59 host1 systemd[1]: Started nova-compute service.
Aug 7 12:08:02 host1 systemd[1]: Stopping nova-compute service...
Aug 7 12:08:02 host1 systemd[1]: Stopped nova-compute service.
Aug 7 12:08:02 host1 systemd[1]: nova-compute.
Using masakari-
Aug 7 16:17:33 host1 masakari-
Aug 7 16:17:33 host1 masakari-
Checking our process list of the system we found the nova-process:
:~# ps uax | grep nova
nova 38205 2.2 0.0 2618068 168120 ? Ssl 16:20 0:05 /openstack/
From this we deduced that the masakari-
After updating our venv the actual path and the path masakari-
This behavior is obviously harmfull.
Especially in case of openstack-ansible there is a long time between the calls of os-nova-install.yml and os-masakri-
- import_playbook: os-keystone-
...
- import_playbook: os-nova-install.yml
- import_playbook: os-neutron-
- import_playbook: os-heat-install.yml
- import_playbook: os-horizon-
- import_playbook: os-designate-
- import_playbook: os-gnocchi-
- import_playbook: os-swift-
- import_playbook: os-ceilometer-
- import_playbook: os-aodh-install.yml
- import_playbook: os-panko-
- import_playbook: os-ironic-
- import_playbook: os-magnum-
- import_playbook: os-trove-
- import_playbook: os-sahara-
- import_playbook: os-octavia-
- import_playbook: os-tacker-
- import_playbook: os-blazar-
- import_playbook: os-masakari-
...
The bug will be fixed eventually (if configuration of OSA is ok) during the runtime of setup-openstack
Nonetheless ALL openstack-
This has to be fixed ASAP, pls.