Bug 2058644

Summary: When updating docker from 161 to 209 we get some "zombie" container left on the environment.
Product: Red Hat Enterprise Linux 7 Reporter: Sofer Athlan-Guyot <sathlang>
Component: dockerAssignee: Kir Kolyshkin <kir>
Status: CLOSED NOTABUG QA Contact: Alex Jia <ajia>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.9CC: amurdaca, dmaley, dornelas, dwalsh, jpretori, jschluet, kir, lsm5, mburns, mciecier, pthomas, smccarty, tsweeney, ypu
Target Milestone: rcKeywords: Extras, Regression, Reopened
Target Release: ---   
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: 2022-03-15 21:02:51 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:
Bug Depends On:    
Bug Blocks: 2058636    

Description Sofer Athlan-Guyot 2022-02-25 14:17:41 UTC
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:

Comment 7 Daniel Walsh 2022-02-26 18:19:05 UTC
Since RHEL7 is not getting updates this will not be fixed.

Comment 8 Jon Schlueter 2022-03-07 18:08:47 UTC
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

Comment 10 Daniel Walsh 2022-03-09 15:22:17 UTC
You need to go through product management.  If it was up to me, I would not update Docker at all.

Comment 12 Tom Sweeney 2022-03-10 15:46:41 UTC
@smccarty (PM for containers), care to weigh in on how to handle this one?  Please see above comment stream.

Comment 13 Daniel Walsh 2022-03-10 19:22:52 UTC
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.

Comment 18 Red Hat Bugzilla 2023-09-15 01:22:26 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days