Bug 1836978

Summary:	Please backport correction patch for the native container healthchecks [container-tools-2.0-8.2.0]
Product:	Red Hat Enterprise Linux 8	Reporter:	Jindrich Novy <jnovy>
Component:	podman	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	atomic-bugs, bbaude, cjeanner, ddarrah, dornelas, dwalsh, imcleod, jligon, jnovy, kanderso, lsm5, mheon, pthomas, santiago, tsweeney
Target Milestone:	rc	Flags:	santiago: needinfo- pm-rhel: mirror+
Target Release:	8.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	podman-1.6.4-12.el8_2_0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1834346	Environment:
Last Closed:	2020-06-10 09:21:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1834346
Bug Blocks:	1727325, 1734579

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