DevStack "stack.sh" sometimes fails after "unstack.sh"
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kuryr-kubernetes |
Fix Released
|
Medium
|
Antoni Segura Puimedon |
Bug Description
Steps to reproduce:
1. stack.sh (successful)
2. restart host
3. unstack.sh
4. stack.sh (failing)
Workaround:
Run unstack.sh+stack.sh again after failure occurs.
DevStack output:
2016-11-03 11:30:25.436 | ++ /opt/stack/
etcd:/var/etcd:rw quay.io/
://172.
40.11:2379 --initial-
2016-11-03 11:30:25.441 | ++ /opt/stack/
2016-11-03 11:30:25.442 | ++ /opt/stack/
2016-11-03 11:30:25.444 | ++ /opt/stack/
2016-11-03 11:30:25.445 | ++ /opt/stack/
-volume=
se-peer-urls http://
s http://
te new
2016-11-03 11:30:25.453 | docker: Error response from daemon: Conflict. The name "/etcd" is already in use by container b77530f9463a075
c90af27776ec2d2
2016-11-03 11:30:25.456 | See 'docker run --help'.
description: | updated |
Changed in kuryr-kubernetes: | |
assignee: | nobody → Daniel Mellado (daniel-mellado) |
Changed in kuryr-kubernetes: | |
milestone: | none → pike-2 |
Yes, I hit this one too. Just by removing the docker etcd container (docker rm etcd_id) it works