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.
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