Bug 1812125

Summary:	Podman can't reuse container name, even if container is not around
Product:	Red Hat Enterprise Linux 8	Reporter:	Telles Nobrega <tenobreg>
Component:	podman	Assignee:	Matthew Heon <mheon>
Status:	CLOSED WORKSFORME	QA Contact:	atomic-bugs <atomic-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	8.1	CC:	bbaude, dwalsh, jligon, jnovy, lsm5, mheon, tsweeney
Target Milestone:	rc
Target Release:	8.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-06-05 17:19:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Telles Nobrega 2020-03-10 15:01:10 UTC

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* "

Comment 2 Tom Sweeney 2020-06-05 17:19:16 UTC

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.