Bug 1761867 - [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
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-paunch
Version: 15.0 (Stein)
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Cédric Jeanneret
QA Contact: nlevinki
Depends On: 1761865 1769206
Blocks: 1761870
TreeView+ depends on / blocked
Reported: 2019-10-15 13:29 UTC by Lon Hohberger
Modified: 2023-03-24 15:41 UTC (History)
13 users (show)

Fixed In Version: python-paunch-4.5.2-0.20191015141456.2875dad.el8ost
Doc Type: No Doc Update
Doc Text:
Clone Of: 1761865
: 1761870 (view as bug list)
Last Closed: 2019-12-02 10:11:16 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
OpenStack gerrit 688705 0 'None' MERGED Use k8s-file log driver with podman 2020-03-23 06:04:30 UTC
Red Hat Knowledge Base (Solution) 4553331 0 None None None 2019-11-06 09:27:12 UTC
Red Hat Product Errata RHBA-2019:4030 0 None None None 2019-12-02 10:11:54 UTC

Internal Links: 1768930

Description Lon Hohberger 2019-10-15 13:29:17 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): 

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 10 Salman Khan 2019-11-22 00:51:48 UTC
any progress here?

Comment 19 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.


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