It seems libvirt package in Ubuntu 22.04 uses the kvm group instead of the libvirt-qemu group when launching a qemu process.
Because of this change and the default behavior of libvirt which makes all image files chowned by the group/user to run qemu process, the instance files are owned by the kvm group, instead of the libvirt-qemu group.
However currently the nova user is still added to the libvirt-qemu group instead of the kvm group.
Because of this inconsistency nova can't access to instance image once the files are chowned to the kvm group.
nova 3:26.1.0-0ubuntu1~cloud0
libvirt 8.0.0-1ubuntu7.4
It seems libvirt package in Ubuntu 22.04 uses the kvm group instead of the libvirt-qemu group when launching a qemu process.
Because of this change and the default behavior of libvirt which makes all image files chowned by the group/user to run qemu process, the instance files are owned by the kvm group, instead of the libvirt-qemu group.
However currently the nova user is still added to the libvirt-qemu group instead of the kvm group.
Because of this inconsistency nova can't access to instance image once the files are chowned to the kvm group.
nova 3:26.1. 0-0ubuntu1~ cloud0
libvirt 8.0.0-1ubuntu7.4
I've found the problem in puppet jobs. (example https:/ /zuul.opendev. org/t/openstack /build/ d6f2fb2e92ad4ec e86bcd3d8793bf9 20 ) /2e4f6457af6d4b b29c73- cc818d493c2a52e f4d37701157d677 02.ssl. cf2.rackcdn. com/877214/ 2/check/ puppet- openstack- integration- 7-scenario002- tempest- ubuntu- jammy/d6f2fb2/ logs/nova/ nova-compute. txt
Example error in nova can be found here: https:/
I've tested adding the nova user to the kvm group and confirmed this fixes the error. /review. opendev. org/c/openstack /puppet- openstack- integration/ +/877338
https:/