Bug 2022736

Summary: [OSP16.1] qemu logs are not accessible on the host
Product: Red Hat OpenStack Reporter: Bogdan Dobrelya <bdobreli>
Component: openstack-tripleo-heat-templatesAssignee: Bogdan Dobrelya <bdobreli>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: medium Docs Contact:
Priority: medium    
Version: 16.1 (Train)CC: achernet, alifshit, apevec, bdobreli, jhakimra, lhh, mburns, tkajinam
Target Milestone: z8Keywords: Patch, Regression, Triaged
Target Release: 16.1 (Train on RHEL 8.2)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-tripleo-heat-templates-11.3.2-1.20220114223343.29a02c1.el8ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2022691 Environment:
Last Closed: 2022-03-24 11:02:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version: Wallaby
Embargoed:

Description Bogdan Dobrelya 2021-11-12 13:23:57 UTC
+++ This bug was initially created as a clone of Bug #2022691 +++

+++ This bug was initially created as a clone of Bug #2005340 +++

Description of problem:
They should be in /var/log/containers/libvirt/qemu

--- Additional comment from Bogdan Dobrelya on 2021-09-21 08:16:37 UTC ---

t-h-t bind mounts it into /var/log/libvirt/qemu/ on the host. Please recheck if anything else is missing? And I can see no logs in /var/log/qemu in containers.

--- Additional comment from Bogdan Dobrelya on 2021-09-27 09:24:49 UTC ---

I can see the instances logs in /var/log/libvirt/qemu on host, like if something escapes the nova_libvirt container context and ignores the /var/log/containers/libvirt/ bind mount

Comment 1 Bogdan Dobrelya 2021-11-29 17:07:42 UTC
*** Bug 1972556 has been marked as a duplicate of this bug. ***

Comment 12 errata-xmlrpc 2022-03-24 11:02:17 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 (Red Hat OpenStack Platform 16.1.8 bug fix and enhancement advisory), 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/RHBA-2022:0986