ntp: Remove removal of chrony container
The chrony container removal was performed in the Xena cycle, so we no longer require this task in the 'overcloud host configure' command. Change-Id: I86fcc75e844eb922f62c90c45a105519845cc1a7
This commit is contained in:
parent
01e5834ed1
commit
06123b795d
@ -17,23 +17,3 @@
|
||||
state: "{{ 'stopped' if service_exists else omit }}"
|
||||
become: true
|
||||
with_items: "{{ ntp_service_disable_list }}"
|
||||
|
||||
- name: Remove kolla-ansible installed chrony container
|
||||
shell:
|
||||
cmd: >
|
||||
if [[ -n $(docker ps -aq -f name=chrony) ]]; then
|
||||
docker rm -f -v chrony
|
||||
fi
|
||||
executable: "/bin/bash"
|
||||
register: result
|
||||
changed_when: result.stdout != ""
|
||||
become: true
|
||||
# NOTE(wszumski): There is an ordering issue where on a fresh host, docker
|
||||
# will not have been configured, but if that is the case, the chrony container
|
||||
# can't possibly exist, but trying to execute this unconditionally will fail
|
||||
# with: No module named 'docker' as we have not yet added the docker package
|
||||
# to the kayobe target venv, so we use 'docker rm' command with force and
|
||||
# don't fail on error.
|
||||
when:
|
||||
- "'docker.service' in ansible_facts.services"
|
||||
- ansible_facts.services['docker.service'].status == 'running'
|
||||
|
Loading…
Reference in New Issue
Block a user