Bug 1679858
| Summary: | [upgrades][13->14] Overcloud upgrade getting stuck on docker restart | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Archit Modi <amodi> |
| Component: | python-docker | Assignee: | RHOS Maint <rhos-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | RHOS Maint <rhos-maint> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 14.0 (Rocky) | CC: | jfrancoa, lyarwood, mburns |
| Target Milestone: | --- | Keywords: | ZStream |
| 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: | 2019-06-12 13:00:53 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
Archit Modi
2019-02-22 04:30:18 UTC
Overcloud upgrade gets stuck in the below task at the docker restart step: 2019-02-20 06:33:15,247 p=3197 u=mistral | TASK [Remove any container using the same Mariadb image] *********************** 2019-02-20 06:33:15,247 p=3197 u=mistral | Wednesday 20 February 2019 06:33:15 -0500 (0:00:00.682) 0:24:33.361 **** Docker gets hung and has be aborted by Ctrl+C as shown: [heat-admin@controller-0 ~]$ sudo docker ps ^C We are facing the same issue with the latest passed_phase1 puddle: [root@controller-1 ~]# time timeout 30 docker ps real 0m30.004s user 0m0.014s sys 0m0.028s [root@controller-2 ~]# time timeout 30 docker ps real 0m30.004s user 0m0.017s sys 0m0.016s (undercloud) [stack@undercloud-0 ~]$ ssh heat-admin.24.14 Warning: Permanently added '192.168.24.14' (ECDSA) to the list of known hosts. Last login: Thu Mar 7 12:13:36 2019 from 192.168.24.1 [heat-admin@controller-0 ~]$ sudo docker ps We can close this bug now that the problematic docker package has been updated *** This bug has been marked as a duplicate of bug 1671861 *** |