Bug 1967878

Summary: [16.2] Make podman events log to the journal and not to a file
Product: Red Hat OpenStack Reporter: Michele Baldessari <michele>
Component: tripleo-ansibleAssignee: Michele Baldessari <michele>
Status: CLOSED ERRATA QA Contact: Joe H. Rahme <jhakimra>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 16.2 (Train)CC: aschultz, cjeanner, drosenfe, fbaudin, jpretori, shrjoshi, spower
Target Milestone: rcKeywords: Triaged
Target Release: 16.2 (Train on RHEL 8.4)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tripleo-ansible-0.7.1-2.20210603175836.el8ost.5 openstack-tripleo-heat-templates-11.5.1-2.20210603174816.el8ost.4 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-09-15 07:15:41 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:

Comment 10 David Rosenfeld 2021-06-30 22:37:01 UTC
1. In default deployment:

[heat-admin@controller-0 ~]$ more /etc/containers/containers.conf

[containers]
pids_limit = 4096
[engine]
events_logger = "journald"

[heat-admin@controller-0 ~]$ sudo ls -lrt /run/libpod/events
total 0

In standard deployment events.log is no longer being filled with podman events.


2. In a deployment where podman-baremetal-ansible.yaml updated to log to a file:

heat-admin@controller-0 ~]$ more /etc/containers/containers.conf

[containers]
pids_limit = 4096
[engine]
events_logger = "file"


sudo ls -lrt /run/libpod/events
total 1288
-rw-r--r--. 1 root root       0 Jun 30 18:45 events.log.lock
-rwx------. 1 root root 1317168 Jun 30 19:09 events.log

a few minutes later:

sudo ls -lrt /run/libpod/events
total 1644
-rw-r--r--. 1 root root       0 Jun 30 18:45 events.log.lock
-rwx------. 1 root root 1683401 Jun 30 19:15 events.log

Logging to a file may be enabled if needed.

Comment 13 errata-xmlrpc 2021-09-15 07:15:41 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 (RHOSP) 16.2 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/RHEA-2021:3483