Open Stack

Dear Operators of Kolla-based deployments,

There is a critical regression in current Kolla Ansible Wallaby code
that results in an environment that shuts down VMs on each libvirtd
container stop or restart on non-cgroupsv2 distros (so CentOS, Ubuntu
and Debian Buster but not Debian Bullseye). [1]

The fix is already available. [2]
Please apply it to your Kolla Ansible installation if you are using Wallaby.
Do note the fix only applies after redeploying which means
redeployment action will still trigger the buggy behaviour that once!

What to do if you have already deployed Wallaby?
First of all, make sure you don't accidentally take an action that
stops nova_libvirt (including restarts: both manual and those applied
by Kolla Ansible due to user-requested changes).
Please apply the patch above but don't rush with redeploying!
Redeploy each compute node separately (or in batches if you prefer) -
using --limit commandline parameter - and always make sure you have
first migrated relevant VMs out of the nodes that are going to get
nova_libvirt restarted.
This way you can safely fix an existing deployment.

We will be working on improving the testing to avoid such issues in the future.

Acknowledgements
Thanks to Ignazio Cassano for noticing and reporting the issue.
I have triaged and analysed it, proposing a fix afterwards.

[1] https://bugs.launchpad.net/kolla-ansible/+bug/1941706
[2] https://review.opendev.org/c/openstack/kolla-ansible/+/806476

-yoctozepto