Bug 1872263

Summary: Update podman to 2.0.5
Product: Red Hat Enterprise Linux 8 Reporter: Jindrich Novy <jnovy>
Component: podmanAssignee: Jindrich Novy <jnovy>
Status: CLOSED ERRATA QA Contact: atomic-bugs <atomic-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.3CC: bbaude, dwalsh, imcleod, jligon, jnovy, lsm5, mheon, pvlasin, santiago, ypu
Target Milestone: rc   
Target Release: 8.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: podman-2.0.5-1.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-04 03:06:49 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: 1827794, 1866153    

Description Jindrich Novy 2020-08-25 10:06:52 UTC 
The plan is to update to podman-2.0.5 which was just released in 8.3.0:

https://github.com/containers/podman/releases/tag/v2.0.5

Due to release cycle of 8.3.0 we might want to go through the exception approval.
Comment 8 Ed Santiago 2020-08-27 18:16:22 UTC 
Yes, I sent you email about that on 2020-08-19, subject "Heads-up: 'buildInfo' definition will be needed ..."
Comment 14 Daniel Walsh 2020-08-28 14:32:54 UTC 
I know that there will be a podman 2.0.6 release to fix the systemd on cgroupv1 issue.

Fixed in master

https://github.com/containers/podman/pull/7475
Comment 16 Joy Pu 2020-09-28 04:04:01 UTC 
As podman packcage for rhel8 stream is already update to 2.0.5 set this to verified.
Comment 19 errata-xmlrpc 2020-11-04 03:06:49 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 (Moderate: container-tools:rhel8 security, bug fix, and enhancement update), 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:4694