Colelctd Sensubility doesn't work on OSP17.1 and RHEL8. latest collectd is collectd-5.12.0-10.el8ost This scenario ma only happen after FFU in Mixed RHEL environment when compute node(s) are RHEL8. Clean OSP17.1 this scenario won't happen. The error that I get in sensubility.log --------------------------------------- \\\"/scripts/collectd_check_health.py\\\", line 91, in \\u003cmodule\\u003e\\n rc, status = fetch_container_health(o.decode())\\n File \\\"/scripts/collectd_check_health.py\\\", line 74, in fetch_container_health\\n if len(item['healthy']) \\u003e 0 and item['status'] != 'stopped':\\nTypeError: object of type 'NoneType' has no len()\\n\",\"status\":\"1\"}}}"},"startsAt":"2023-07-14T11:12:27Z"}}] [DEBUG] Requesting execution of check. [check: check-container-health] [DEBUG] Executed check script. [output: Traceback (most recent call last): File "/scripts/collectd_check_health.py", line 91, in <module> rc, status = fetch_container_health(o.decode()) File "/scripts/collectd_check_health.py", line 74, in fetch_container_health if len(item['healthy']) > 0 and item['status'] != 'stopped': TypeError: object of type 'NoneType' has no len() The problem is that healthcheck script is using podman inspect <container-name> command, which apparently changed output. Workaround: ----------- To change /var/lib/container-config-scripts/collectd_check_health.py on line 26 s/“healthy: .State.Health.Status}“/ “healthy: .State.Healthcheck.Status}“/
Even when imfile is loaded and no output module is loaded, the rsyslog container fails to start [1]. Failure to configure even single output module is configuration issue not a bug. [1] rsyslogd: there are no active actions configured. Inputs would run, but no output whatsoever were created. [v8.2102.0-15.el8 try https://www.rsyslog.com/e/2103 ] rsyslogd: run failed with error -2103 (see rsyslog.h or try https://www.rsyslog.com/e/2103 to learn what that number means)
Wrong BZ, sorry.
Script "collectd_check_health.py" is working good in OSP17.1z2 deployment.. Need to deploy OSP16.2 with Rhel8.4 and verify it works on the same.
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:0185