Description of problem: In Undercloud, the "ironic_pxe_tftp" container is showing an unhealthy status Version-Release number of selected component (if applicable): - Red Hat Enterprise Linux release 9.0 Beta (Plow) - Puddle: RHOS-17.0-RHEL-9-20220214.n.1 How reproducible: Scale lab Steps to Reproduce: 1. Container status in podman $ sudo podman ps|grep ironic_pxe_tftp 9da75c26599c undercloud.ctlplane.localdomain:8787/rh-osbs/rhosp17-openstack-ironic-pxe:17.0_20220210.1_9 /bin/bash -c BIND... 6 hours ago Up 6 hours ago (unhealthy) ironic_pxe_tftp 2. container health check $ sudo podman exec -it -u root ironic_pxe_tftp "openstack/healthcheck" WARN[0000] Failed to add conmon to systemd sandbox cgroup: Unit libpod-conmon-9da75c26599cc764c46d17bc60b178ee266b14dcc57e24e34edece01d863fcaa.scope already exists. curl: (1) Protocol "tftp" not supported or disabled in libcurl 000 :0 0.000000 seconds 3. Inspect log $ sudo podman inspect ironic_pxe_tftp ... "State": { "OciVersion": "1.0.2-dev", "Status": "running", "Running": true, "Paused": false, "Restarting": false, "OOMKilled": false, "Dead": false, "Pid": 30683, "ConmonPid": 30680, "ExitCode": 0, "Error": "", "StartedAt": "2022-02-25T07:00:29.204361735Z", "FinishedAt": "0001-01-01T00:00:00Z", "Healthcheck": { "Status": "unhealthy", "FailingStreak": 644, "Log": [ { "Start": "2022-02-25T12:30:22.154347209Z", "End": "2022-02-25T12:30:22.406390946Z", "ExitCode": 1, "Output": "" }, ... Actual results: ironic_pxe_tftp container is in unhealthy status Expected results: ironic_pxe_tftp container should be healthy status
I had a look at curl, and it seems that the rpm "curl-minimal' was installed. If the package 'curl' is installed instead, the libcurl will have tftp enabled and this healthcheck will not fail. Both curl and curl-minimal is in available in RHEL 9.
I still think we should treat this like the dnsmasq healthcheck, and remove it as not adding value.
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 (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), 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-2022:6543