Collectd sensubility stops working after overcloud node was rebooted. It happens because while deploying overcloud we are setting collectd user to be able to run /run/podman and apparently setfacl does not survive reboot. After rebooting overcloud node I am getting following messages in sensubility log file: podman machine init` and `podman machine start` to manage a new Linux VM\\n Error: unable to connect to Podman socket: Get \\\"http://d/v4.4.1/libpod/_ping\\\": dial unix ///run/podman/podman.sock: connect: permission denied\\n\\n\",\"status\":\"1\"}}}"},"startsAt":"2023-05-15T04:01:11Z"}}] [DEBUG] Sent message ACKed. [id: 136] [DEBUG] Requesting execution of check. [check: check-container-health] [DEBUG] Executed check script. [output: Failed to list containers:
The work around is after rebooting overcloud node manually run a following command: sudo podman exec -it collectd setfacl -R -m u:collectd:rwx /run/podman
This is a high severity/priority issue and it is already modified. Moving back to z1.
Verified openstack-tripleo-heat-templates-14.3.1-17.1.20231103010823.el9ost.noarch
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 17.1.2 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-2024:0209