Overcloud deployment failed because of docker-puppet-crond container conflict
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Emilien Macchi |
Bug Description
Overcloud deployment has failed with this message:
2018-10-19 14:46:51 | "2018-10-19 18:34:10,726 ERROR: 19339 -- Failed running docker-puppet.py for crond",
2018-10-19 14:46:51 | "2018-10-19 18:34:10,726 ERROR: 19339 -- /usr/bin/
2018-10-19 14:46:51 | "See '/usr/bin/
while processing compute-0 node. Deployment command line:
openstack overcloud deploy \
--templates /usr/share/
--libvirt-type kvm --control-flavor baremetal --compute-flavor baremetal --ceph-
There's no trace of any container in every node (both controllers and computes). The "docker ps" and "docker ps -a" commands output are empty.
tags: | added: queens-backport-potential |
tags: | added: pike-backport-potential |
tags: | added: idempotency |
Changed in tripleo: | |
assignee: | Steve Baker (steve-stevebaker) → Emilien Macchi (emilienm) |
status: | Triaged → In Progress |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
docker-puppet.py should use unique container names always, and auto --rm on exit