Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

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.

Description of problem:

`podman images` can panic when the storage contains an incoherent/incomplete image.

Version-Release number of selected component (if applicable):
podman 2.0.5 and following.


Steps to Reproduce:
Following the steps provided in https://github.com/containers/podman/issues/7444:

1. Start `podman build`.
2. Kill the build process during a build step.
3. Run `podman images`.

Actual results:

Panic.


Expected results:

Listing of images.

Additional info:

It's fixed upstream with https://github.com/containers/podman/pull/7554 and the referenced commit but we need a BZ to backport to 2.0. It seems fairly likely that build processes are killed manually by users, so I think we should get it fixed in RHEL as well.

Upstream PR (backport to v2.0): https://github.com/containers/podman/pull/7556

Yes this should be fixed in RHEL8.3
We have another bunch of fixes that RHEL QE is finding going in, so we should fix them as breaking existing functionality.

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-2021:0531