Bug 2141019

Summary:	Update podman to 4.2.1 or 4.3.0
Product:	Red Hat Enterprise Linux 9	Reporter:	Philipp Trulson <philipp>
Component:	podman	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED ERRATA	QA Contact:	Joy Pu <ypu>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	CentOS Stream	CC:	bbaude, bstinson, dwalsh, jnovy, jwboyer, lsm5, mboddu, mheon, pthomas, tsweeney, umohnani, ypu
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	podman-4.3.1-3.el9	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-09 07:41:58 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:

Description Philipp Trulson 2022-11-08 13:18:51 UTC

Description of problem:

We are using podman on CentOS Stream 9 for our CI infrastructure. Podman 4.2.1 was released over 2 months ago and contains a critical fix for us, however it hasn't arrived in the package repos yet. We specifically chose Stream to get updates faster - can you maybe explain the update schedule/policy for the whole podman/buildah/skopeo stack? Is there some kind of testing repo?

It would be really great if updates for this would be pushed faster.

Comment 1 Jindrich Novy 2022-11-08 14:05:16 UTC

Phillip, it is now just a matter of paperwork. It should appear in c9s after filing advisories.

Comment 2 Philipp Trulson 2022-11-08 15:03:40 UTC

Thanks for the quick reply Jindrich! For future reference - does it always take 2 months for paperwork? Did it take longer because you were busy/there were issues with packaging? We just want to know what delay to expect for future releases.

Comment 3 Jindrich Novy 2022-11-09 13:05:54 UTC

Phillip, there are multiple moving parts, e.g. currently failing gating tests. These need to get addressed before the new podman-4.3.0 can appear in c9s so that only stable content in c9s. I will update this bug once these are no longer an issue - which means you can update to podman-4.3.0 in c9s. If you'd like to test 4.3.0 and newer container-tools I suggest to try Fedora. Thank you for understanding.

Comment 4 Philipp Trulson 2022-11-30 11:13:15 UTC

Package is available now, issue can be closed.

Comment 5 Jindrich Novy 2022-11-30 11:22:50 UTC

Thank you fo confirmation Philipp!

Comment 8 Joy Pu 2023-02-27 10:08:37 UTC

Podman in RHEL 9.2 actually updated to 4.4 So move this to verified.

Comment 10 errata-xmlrpc 2023-05-09 07:41:58 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: podman security and bug fix 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-2023:2282