RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2014149 - Container does not start on RHCOS 4.8.2 with podman
Summary: Container does not start on RHCOS 4.8.2 with podman
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-14 14:09 UTC by Gianluca Villani
Modified: 2022-03-03 13:40 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-03 13:40:18 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-100887 0 None None None 2021-10-27 13:02:47 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.