Bug 2014149

Summary:	Container does not start on RHCOS 4.8.2 with podman
Product:	Red Hat Enterprise Linux 8	Reporter:	Gianluca Villani <gvillani>
Component:	podman	Assignee:	Jindrich Novy <jnovy>
Status:	CLOSED CURRENTRELEASE	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.4	CC:	aos-bugs, bbaude, dornelas, dwalsh, jligon, jnovy, lsm5, mheon, pthomas, skrenger, tsweeney, umohnani, vrothber
Target Milestone:	rc	Flags:	pm-rhel: mirror+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-03-03 13:40:18 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:

Comment 1 Tom Sweeney 2021-10-14 17:15:02 UTC

@gvillani Can you please provide more information on how to reproduce this.  Specifically the command(s) that were used to pull down the container image and to then build/run the container please?

Comment 4 Tom Sweeney 2021-10-15 21:38:48 UTC

Not completed this sprint

Comment 5 Tom Sweeney 2021-10-20 00:00:16 UTC

@gvillani thanks for the follow-up.  I think this probably should have been reported against Podman and RHEL 8 correct?  Is there a tie in with OCP on the customer site?  Regardless, I'm assigning this to @vrothber to take a look at.

Comment 6 Gianluca Villani 2021-10-20 08:46:24 UTC

Hi Tom,


Thanks for the clarification, Honestly I was not sure which products I should have chosen for this bug.

Kind regards

Gianluca Villani

Comment 7 Tom Sweeney 2021-10-20 13:49:34 UTC

Gianluca, thanks for the info, and no worries.  I'll go change the component to make sure the right group of people see the progress of this BZ.  Also this looks to be running a dev version of Podman that accidentally leaked.  This may be fixed already, but I'll let Valentin confirm

Comment 13 Daniel Walsh 2021-10-28 15:11:04 UTC

Well I guess I would say the earliest version we have a complaint and then all newer versions.  I just want to avoid busy work.
Do we update minor releases after they are released?  IE 8.4.0.2, 8.5.0.2, or do we just tell the customer to update to 8.5 or 8.6 version?

Comment 14 Matthew Heon 2021-10-28 18:19:22 UTC

Depends on stream. RHEL8 stream, AFAIK, only provides support for the latest release; 3.0 stream will require backports, but that is also only Podman 3.0.2 for every release.