Bug 1768930

Summary:	backport json-file logging support to 1.4.2
Product:	Red Hat Enterprise Linux 8	Reporter:	Christopher Brown <chris.brown>
Component:	podman	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	8.1	CC:	bbaude, ddarrah, dornelas, dwalsh, jlabarre, jligon, jnovy, lsm5, mheon, toneata, tsweeney, weshen, ypu
Target Milestone:	rc	Keywords:	ZStream
Target Release:	8.2
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL 8.2, Podman 1.6.3, Podman 1.4.2-stable3, podman-1.4.2-7.el8_1_0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1770176 1779789 (view as bug list)		Environment:
Last Closed:	2020-04-28 15:48:34 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:
Bug Blocks:	1186913, 1734579, 1770176, 1779789

Description Christopher Brown 2019-11-05 15:12:25 UTC

Description of problem:

https://github.com/containers/libpod/issues/3363

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

1.4.2

How reproducible:

OSP 15 installation is broken due to https://github.com/containers/libpod/issues/3363

If we are not pushing a zero-day update to 1.4.3 please can we backport this fix.

I also note that podman in RHEL 7 is newer (1.4.4) than in RHEL 8 (1.4.2).

Comment 2 Daniel Walsh 2019-11-05 19:59:11 UTC

There were be a new version in three Months podman 1.6.3 or greater.

Comment 3 Christopher Brown 2019-11-05 20:55:11 UTC

(In reply to Daniel Walsh from comment #2)
> There were be a new version in three Months podman 1.6.3 or greater.

To me this lends more weight to the argument for fixing in 1.4.2, especially given the trivial nature of the fix.

Comment 6 Craig Reeves 2019-11-06 21:12:57 UTC

(In reply to Christopher Brown from comment #3)
> (In reply to Daniel Walsh from comment #2)
> > There were be a new version in three Months podman 1.6.3 or greater.
> 
> To me this lends more weight to the argument for fixing in 1.4.2, especially
> given the trivial nature of the fix.

+1 this is painful

Comment 7 Daniel Walsh 2019-11-06 21:16:17 UTC

The painful part of this is that it is being reported after the freeze.

Comment 8 Christopher Brown 2019-11-06 21:52:15 UTC

(In reply to Daniel Walsh from comment #7)
> The painful part of this is that it is being reported after the freeze.

Incorrect: https://github.com/containers/libpod/issues/3363

Comment 10 Daniel Walsh 2019-11-07 02:48:50 UTC

Sure that got fixed in master, but no one checked if it was in the release until this week.  Jun 19 was 4 5 months ago.

Comment 20 James E. LaBarre 2019-11-22 17:11:03 UTC

If it's of any use, I've been encountering this problem on my multi-arch (Power8) test environment as well.  Not that the problem is showing up on the Power node, it never gets that far ("podman run" fails while trying to set up the Controller node).  My mistake was presuming the Controller would have the same package versions as the Director (running RHEL 8.0).

While trying to track down the problem, I saved off a few overcloud deploy logs with the "--debug" switch, if they could be of any use to someone.  Or, since I have to wait for this to get resolved anyway, my system would be available for a test build.

Comment 30 errata-xmlrpc 2020-04-28 15:48:34 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/RHSA-2020:1650