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 1768930 - backport json-file logging support to 1.4.2
Summary: backport json-file logging support to 1.4.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.1
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: 8.2
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1186913 1734579 1770176 1779789
TreeView+ depends on / blocked
 
Reported: 2019-11-05 15:12 UTC by Christopher Brown
Modified: 2023-03-24 15:54 UTC (History)
13 users (show)

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:
Clone Of:
: 1770176 1779789 (view as bug list)
Environment:
Last Closed: 2020-04-28 15:48:34 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1761867 0 urgent CLOSED [RHEL 8.1] Podman dropped json-file log format in favor of k8s-file 2023-03-24 15:41:34 UTC
Red Hat Issue Tracker RHELPLAN-29126 0 None None None 2022-04-25 23:32:52 UTC
Red Hat Product Errata RHSA-2020:1650 0 None None None 2020-04-28 15:51:03 UTC

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
Note You need to log in before you can comment on or make changes to this bug.