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:

Using podman 1.6.4 I'm hitting an issue where podman can't start a new container even if the old container with same name is non existing anymore.


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

Podman 1.6.4
RHEL 8.1

How reproducible:

Happens from time to time, but it is not consistent


Steps to Reproduce:
1. Stop ceph-mon container using systemctl stop ceph-mon*
2. Start ceph-mon container using systemctl start ceph-mon*
3. Verify if the container started

Actual results:

Can't start container because the container already exists

Expected results:

Container starts 

Additional info:

An easy workaround is to run "podman rm --storage ceph-mon* "

As we've not received a response in almost three months to our request and I believe this issue was solved with the solution listed in https://bugzilla.redhat.com/show_bug.cgi?id=1757845, I'm going to close this BZ.  If you're still having issues with this, please reopen or better yet start up a new BZ.