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 2173082 - Podman containers do not start after upgrade to v4.4.1
Summary: Podman containers do not start after upgrade to v4.4.1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: podman
Version: 8.9
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jindrich Novy
QA Contact: Yuhui Jiang
URL:
Whiteboard:
Depends On:
Blocks: 2173089 2176833
TreeView+ depends on / blocked
 
Reported: 2023-02-23 21:53 UTC by Tom Sweeney
Modified: 2023-11-14 16:22 UTC (History)
12 users (show)

Fixed In Version: podman-4.6.1-2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2173089 2176833 (view as bug list)
Environment:
Last Closed: 2023-11-14 15:27:28 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github containers podman pull 17839 0 None closed [v4.4.1-rhel] Vendor c/storage v1.45.4 2023-08-18 09:10:49 UTC
Red Hat Issue Tracker RHELPLAN-149856 0 None None None 2023-02-23 21:56:35 UTC
Red Hat Issue Tracker RHELPLAN-149857 0 None None None 2023-02-23 21:56:37 UTC
Red Hat Product Errata RHSA-2023:6939 0 None None None 2023-11-14 15:28:44 UTC

Description Tom Sweeney 2023-02-23 21:53:36 UTC
Description of problem:
After upgrading from Podman v4.2.1 to 4.4.1, no Podman containers will start.

Version-Release number of selected component (if applicable): v4.4.1


How reproducible:

Upgrade Podman v4.2.1 to v4.4.1 with existing containers and try to run them afterward.

Steps to Reproduce:
1.
2.
3.

Actual results:  
Error: filesystem type 0x13372fc1 reported for /var/lib/containers/storage is not supported with 'overlay': backing file system is unsupported for this graph driver

Expected results:

Successful completion of the podman run command.

Additional info:  Reported on GitHub: https://github.com/containers/storage/issues/1511

Comment 3 Tom Sweeney 2023-03-17 15:37:30 UTC
Setting to Post and assigning to @jnovy for any further BZ and triaging needs.  Fixed upstream with https://github.com/containers/podman/commit/9d93486d21890dd844fef158d0860ace1357f5ae

Comment 4 Jindrich Novy 2023-03-17 17:47:43 UTC
Tom, this needs to be merged to v4.4.1-rhel upstream branch too in order to consider this to 9.2.0 0day.

Comment 13 errata-xmlrpc 2023-11-14 15:27:28 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 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:6939


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