Description of problem: Current bind mounts for nova_virtqemud need to be updated to account for /var/log/swtpm/libvirt/qemu/ Below is the output log for vTPM enabled guest from within the container generating to /var/log/swtpm/libvirt/qemu/instance-000000b0-swtpm.log > [root@compute-1 qemu]# cat instance-000000b0.log.1 > 2022-06-02 13:42:20.765+0000: Starting external device: TPM Emulator > /usr/bin/swtpm socket --daemon --ctrl type=unixio,path=/run/libvirt/qemu/swtpm/115-instance-000000b0-swtpm.sock,mode=0600 --tpmstate > dir=/var/lib/libvirt/swtpm/febdee00-d829-4f92-8441-4abbf6768c77/tpm2,mode=0600 --log file=/var/log/swtpm/libvirt/qemu/instance-000000b0-swtpm.log -- > terminate --tpm2 --pid file=/run/libvirt/qemu/swtpm/115-instance-000000b0-swtpm.pid --key pwdfd=31,mode=aes-256-cbc --migration-key pwdfd=33,mode=aes- > 256-cbc > 2022-06-02 13:42:20.780+0000: shutting down, reason=failed Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. Create a vTPM enabled guest on a RHOS 17 environment 2. 3. Actual results: Logs are only accessible within the nova_virtqemud container Expected results: Logs are accessible on the host Additional info:
Pushing this out of 17.0 for 17.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2023:4577