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.
Bug 1836978 - Please backport correction patch for the native container healthchecks [container-tools-2.0-8.2.0]
Summary: Please backport correction patch for the native container healthchecks [conta...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.2
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: 8.3
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On: 1834346
Blocks: 1727325 1734579
TreeView+ depends on / blocked
 
Reported: 2020-05-18 15:20 UTC by Jindrich Novy
Modified: 2020-06-10 09:21 UTC (History)
15 users (show)

Fixed In Version: podman-1.6.4-12.el8_2_0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1834346
Environment:
Last Closed: 2020-06-10 09:21:58 UTC
Type: Bug
Target Upstream Version:
Embargoed:
santiago: needinfo-
pm-rhel: mirror+


Attachments (Terms of Use)

Comment 5 Ed Santiago 2020-05-18 21:09:18 UTC
Confirmed: podman-1.6.4-12.module+el8.2.0+6669+dde598ec places healthcheck.log under /var/run

Created a container with healthcheck as described in #5915. Ran them under podman 6368 and 6669.
Looked for healthcheck.log.

podman-1.6.4-11.module+el8.2.0+6368+cf16aa14:

   /var/lib/containers/storage/overlay-containers/<sha>/userdata/healthcheck.log

podman-1.6.4-12.module+el8.2.0+6669+dde598ec:

   /var/run/containers/storage/overlay-containers/<sha>/healthcheck.log

That is: the 6669 build places healthcheck.log under /var/run as expected.

Note that I ran no further tests: did not edit /healthcheck script, did not run
multiple containers, did not do anything more than cursory 'podman inspect'.
I only assert that the location of healthcheck.log has changed.

Comment 7 errata-xmlrpc 2020-06-10 09:21:58 UTC
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:2457


Note You need to log in before you can comment on or make changes to this bug.