Bug 1761865 - [RHEL 8.1] Podman dropped json-file log format in favor of k8s-file
Summary: [RHEL 8.1] Podman dropped json-file log format in favor of k8s-file
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Cédric Jeanneret
QA Contact: nlevinki
URL:
Whiteboard:
Depends On:
Blocks: 1761867 1761870 1769206
TreeView+ depends on / blocked
 
Reported: 2019-10-15 13:27 UTC by Lon Hohberger
Modified: 2023-03-24 15:41 UTC (History)
8 users (show)

Fixed In Version: puppet-tripleo-10.5.2-0.20191009160423.fe160dd.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1761867 1769206 (view as bug list)
Environment:
Last Closed: 2019-12-02 10:11:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 684827 0 'None' 'MERGED' 'Update log-driver value for podman' 2019-12-09 05:09:43 UTC
Red Hat Knowledge Base (Solution) 4553331 0 None None None 2019-11-06 09:27:52 UTC
Red Hat Product Errata RHBA-2019:4030 0 None None None 2019-12-02 10:11:54 UTC

Description Lon Hohberger 2019-10-15 13:27:15 UTC 
Description of problem:

Podman 1.4.2 in RHEL 8.1 has dropped --log-driver json-file; must use --log-driver k8s-file

Version-Release number of selected component (if applicable): 
podman-1.4.2-5.module+el8.1.0+4240+893c1ab8.x86_64

How reproducible: 100%

Steps to Reproduce:
1. podman --log-driver json-file [anything else]

Actual results:
"run failed after [conmon:e]: No such log driver json-file"

Expected results: No CLI breakage between minor updates of RHEL
Comment 5 errata-xmlrpc 2019-12-02 10:11:16 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-2019:4030
Note You need to log in before you can comment on or make changes to this bug.