Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
In podman 1.6.4, the native healthcheck might be using the same status file for all containers, as described in this upstream issue:
https://github.com/containers/libpod/issues/5915

This create issues in OSP environment, preventing the use of podman native healthchecks.

Version-Release number of selected component (if applicable):
1.6.4

How reproducible:
Always

Steps to Reproduce:
1. Run multiple containers with healthcheck using $DIRLOG/${container_name}
2. check for the presence of $DIRLOG/healthcheck

(a full reproducer description is available on the github issue)

Actual results:
healthcheck result are unreliable, and the status file might even be corrupted at some point, breacking the whole thing


Expected results:
each container should have its dedicated healthcheck status file

Additional info:
Upstream patch correcting the issue was already backported to podman 1.9, which should be available for rhel-8.2.x due in July. But we can't wait for this release on OSP, we have our Beta coming end of May :(.

Thank you!

Cheers,

C.

Assigning to Brent as he handled the PR.  This may fall more in Jindrich Novy's arena.

Assigning to Matt Heon based on converstations with Brent and Matt.  This may be completed already, but Matt will verify.

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, 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-2020:2456