Bug 2022691

Summary:	[OSP16.2] qemu logs are not accessible on the host
Product:	Red Hat OpenStack	Reporter:	Bogdan Dobrelya <bdobreli>
Component:	openstack-tripleo-heat-templates	Assignee:	Bogdan Dobrelya <bdobreli>
Status:	CLOSED ERRATA	QA Contact:	Arik Chernetsky <achernet>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	16.2 (Train)	CC:	apevec, bdobreli, jhakimra, lhh, mburns
Target Milestone:	z2	Keywords:	Patch, Regression, Triaged
Target Release:	16.2 (Train on RHEL 8.4)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openstack-tripleo-heat-templates-11.6.1-2.20220104004842.31a431d.el8ost	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	2005340
Clones:	2022736 (view as bug list)		Environment:
Last Closed:	2022-03-23 22:29:33 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:
Bug Depends On:	2005340
Bug Blocks:

Description Bogdan Dobrelya 2021-11-12 10:53:03 UTC

+++ 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 14 errata-xmlrpc 2022-03-23 22:29:33 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 (Moderate: Red Hat OpenStack Platform 16.2 (openstack-tripleo-heat-templates) security update), 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/RHSA-2022:0995