summaryrefslogtreecommitdiffstats
path: root/playbooks/aws/openshift-cluster/roles
diff options
context:
space:
mode:
authorMichael Gugino <mgugino@redhat.com>2017-10-10 19:26:21 -0400
committerMichael Gugino <mgugino@redhat.com>2017-10-11 08:55:07 -0400
commit090ba0dbd9bd31be49b66d996a61b936773d65f1 (patch)
tree9146669d44cf0ad4a69adda910ab02f1cfc2a497 /playbooks/aws/openshift-cluster/roles
parentaf04da3ae11cfe5cc80de214a4ec665f1d1676b1 (diff)
downloadopenshift-090ba0dbd9bd31be49b66d996a61b936773d65f1.tar.gz
openshift-090ba0dbd9bd31be49b66d996a61b936773d65f1.tar.bz2
openshift-090ba0dbd9bd31be49b66d996a61b936773d65f1.tar.xz
openshift-090ba0dbd9bd31be49b66d996a61b936773d65f1.zip
Ensure docker service status actually changes
Currently, docker is started during the docker role. If docker is started during the run of the role, the handler to restart docker is not triggered to prevent excess restarts of the docker service. The systemd docker that starts the docker service may report the result of the task as 'changed' even though docker is already running and the state of the service itself does not change. This commit checks the status of the docker service before starting it to ensure that docker was not in an 'active' state according to systemd. If the docker service is already in the 'active' state, the restart handler will trigger and restart docker at the end of the run of the role. Fixes: https://github.com/openshift/origin/issues/16709
Diffstat (limited to 'playbooks/aws/openshift-cluster/roles')
0 files changed, 0 insertions, 0 deletions