The tasks were attempting to stop/start etcd, which would be fine on the stop but on start could actually kick the non-containerized etcd service which happens to be layed down even though it's unused. When the service was requested to start again it would claim the port embedded etcd needs and the master would then fail to come up. Instead use the correct etcd_container service.
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|
||
|