kolla: stopping (or restarting) nova_libvirt causes vm shutdown
Activity
- Marc Schmitt added IncidentActive incident labels
added IncidentActive incident labels
- Marc Schmitt assigned to @risson
assigned to @risson
- Author Contributor
I just pushed https://gitlab.cri.epita.fr/cri/packages/kolla-ansible/-/tags/12.2.0-cri-1, which is the first step towards resolving this.
The procedure to apply the fix is as follows:
-
Disable the compute host:
openstack compute service set <host> nova-compute --disable
-
Migrate all VMs from it one by one
- Make sure there is none left by running
docker exec -it nova_libvirt virsh list
on the compute host.
- Make sure there is none left by running
-
Run
kolla-ansible deploy --limit <host>
with options as specified inkolla/README.md
-
Enable the host with
openstack compute service set <host> nova-compute --enable
Here is the list of the compute nodes on which this fix has been applied:
- compute-1.bm.cri.epita.fr
- compute-2.bm.cri.epita.fr
- compute-3.bm.cri.epita.fr
- compute-4.bm.cri.epita.fr
- compute-5.bm.cri.epita.fr
- compute-6.bm.cri.epita.fr
- compute-7.bm.cri.epita.fr
- compute-8.bm.cri.epita.fr
- compute-9.bm.cri.epita.fr
- compute-13.bm.cri.epita.fr
- compute-14.bm.cri.epita.fr
- compute-15.bm.cri.epita.fr
- compute-16.bm.cri.epita.fr
- compute-17.bm.cri.epita.fr
- compute-18.bm.cri.epita.fr
Edited by Marc Schmitt -
Disable the compute host:
- Marc Schmitt mentioned in merge request !19 (merged)
mentioned in merge request !19 (merged)
- Author Contributor
I'm also running a
kolla-ansible pull
on each host before re-deploying to make sure we're up-to-date. - Author Contributor
And while I'm at it,
apt update && apt upgrade -y && reboot
- Marc Schmitt mentioned in issue #20 (closed)
mentioned in issue #20 (closed)
- Author Contributor
Closed during #20 (closed).
- Marc Schmitt closed
closed
- Marc Schmitt added IncidentResolved label and removed IncidentActive label
added IncidentResolved label and removed IncidentActive label
- Marc Schmitt mentioned in issue #22 (closed)
mentioned in issue #22 (closed)
Please register or sign in to reply