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:

In the context of Openstack containerized (OSP) we do a update of docker.

When the 209 version of docker started to land in rhel we experienced a job failure because a container couldn't start (ceph-mon).

It couldn't start because we had a container which was still running and had a lock on a directory which prevented  ceph-mon from starting.

That container was the previous ceph-mon container but wasn't visible with docker ps.

After kill -9 the process and the container we were able to start the container successfully.

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

What we see in our CI is:

- update from docker <=161 to docker 209 doesn't work correctly and let some ceph-mon container behind.
- update from docker >=162 to docker 209 works correctly
- update from docker <=161 to docker 208 works correctly
- update from docker >=162 to docker 208 works correctly


So going from docker with a version <= 161 to 209 cause the issue all the time.


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Since RHEL7 is not getting updates this will not be fixed.

docker-1.13.1-209.git7d71120.el7_9 - Jan 2022
docker-1.13.1-208.git7d71120.el7_9 - Jun 2021
docker-1.13.1-161.git64e9980.el7_8 - Mar 2020

You need to go through product management.  If it was up to me, I would not update Docker at all.

@smccarty (PM for containers), care to weigh in on how to handle this one?  Please see above comment stream.

I don't believe this is a repeatable bugzilla.  Can you repeat the problem by downgrading and upgrading.  If not, then I am not sure this is something we are likely to fix.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days