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:
When updating podman from 1.0.x to 1.4.2, we have to call "podman system renumber".

It might happen that command "fails" with this error message:

Error: Error shutting down container storage: A layer is mounted: layer is in use by a container

After a quick discussion, it seems this error is not relevant.

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


How reproducible:


Steps to Reproduce:
1. install podman 1.0.x (RHEL-8.0), run some containers
2. upgrade to RHEL-8.1, providing podman 1.4.2
3. run the "podman system renumber"

Actual results:
It might output a misleading error, while everything is done and working fine

Expected results:
It should output the actual state - "success" or whatever it is.

Additional info:
We are trying to provide an ansible playbook for OSP customers, and this error break the logic, preventing to finish the run without real reason. It also mislead people, since they think that something is broken somewhere whereas all is OK.

Upstream patch https://github.com/containers/libpod/pull/4514

I don't see this as a blocker,  If we have a different blocker, then we should add this fix.   Otherwise we fix this for RHEL8.2

Closing as this was fixed in RHEL 8.2 with Podman v1.7.0-RC1

(In reply to Tom Sweeney from comment #4)
> Closing as this was fixed in RHEL 8.2 with Podman v1.7.0-RC1

@

This would require a hell of a justificaion for a back port. Seems like it can easily be handled in a 
Support article.