Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2093312

Summary: [RHOS-17] swtpm logs not bind-mounted to host
Product: Red Hat OpenStack Reporter: James Parker <jparker>
Component: openstack-tripleo-heat-templatesAssignee: Bogdan Dobrelya <bdobreli>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: alifshit, bdobreli, kchamart, mburns, smooney
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-14.3.1-1.20220920001118.2b27b46.el9ost Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-16 01:11:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description James Parker 2022-06-03 13:44:18 UTC
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:

Comment 1 Bogdan Dobrelya 2022-06-23 13:57:24 UTC
Pushing this out of 17.0 for 17.1

Comment 14 errata-xmlrpc 2023-08-16 01:11:21 UTC
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