Restore libvirtd cgroupfs mount

It was removed in [1] as part of cgroupsv2 cleanup.
However, the testing did not catch the fact that the legacy
cgroups behaviour was actually still breaking despite latest
Docker and setting to use host's cgroups namespace.

[1] 286a03bad20955aa4d3f7009cef5856d328b76f1

Closes-Bug: #1941706
Change-Id: I629bb9e70a3fd6bd1e26b2ca22ffcff5e9e8c731

ansible/roles/nova-cell/defaults/main.yml

@@ -346,6 +346,7 @@ nova_libvirt_default_volumes:
   - "/lib/modules:/lib/modules:ro"
   - "/run/:/run/:shared"
   - "/dev:/dev"
+  - "/sys/fs/cgroup:/sys/fs/cgroup"
   - "kolla_logs:/var/log/kolla/"
   - "libvirtd:/var/lib/libvirt"
   - "{{ nova_instance_datadir_volume }}:/var/lib/nova/"

releasenotes/notes/bug-1941706-a8f9e9544f1540e3.yaml

@@ -0,0 +1,13 @@
+---
+critical:
+  - |
+    Fixes a critical bug which caused Nova instances (VMs) using libvirtd
+    (the default/usual choice) to get killed on libvirtd (``nova_libvirt``)
+    container stop (and thus any restart - either manual or done by running
+    Kolla Ansible). It was affecting Wallaby+ on CentOS, Ubuntu and Debian
+    Buster (not Bullseye). If your deployment is also affected, please read the
+    referenced Launchpad bug report, comment #22, for how to fix it without
+    risking data loss. In short: fixing requires redeploying and this will
+    trigger the bug so one has to first migrate important VMs away and only
+    then redeploy empty compute nodes.
+    `LP#1941706 <https://launchpad.net/bugs/1941706>`__