Just disable hostkey checking everywhere

For testing, don't both with hostkey checking. We know ansible does the
right thing is proper ssh host keys are installed.

Change-Id: Ic6dfa63247741f904516897e9d27a2b57a4c2d7e
Signed-off-by: Paul Belanger <pabelanger@redhat.com>
This commit is contained in:
Paul Belanger 2019-03-28 11:04:55 -04:00
parent 0829dcf7bb
commit c548ce678b
1 changed files with 8 additions and 8 deletions

View File

@ -1,14 +1,6 @@
---
- hosts: all
tasks:
# TODO(pabelanger): Because we use ansible, to install ansible, we first
# need to run windmill-ops, like we do with the current launch-node.py
# script. However, limit it to only the bastion host.
- name: Bootstrap bastion node using windmill-ops
args:
chdir: "{{ zuul.projects['git.openstack.org/openstack/windmill-ops'].src_dir }}"
shell: "tox -evenv -- ansible-playbook -v -f1 playbooks/bootstrap/site.yaml --limit bastion"
# NOTE(pabelanger): In production, this is not needed as the previous
# playbooks will properly setup SSH host keys from the inventory file.
- name: Disable SSH hostkey checking
@ -17,3 +9,11 @@
section: defaults
option: host_key_checking
value: false
# TODO(pabelanger): Because we use ansible, to install ansible, we first
# need to run windmill-ops, like we do with the current launch-node.py
# script. However, limit it to only the bastion host.
- name: Bootstrap bastion node using windmill-ops
args:
chdir: "{{ zuul.projects['git.openstack.org/openstack/windmill-ops'].src_dir }}"
shell: "tox -evenv -- ansible-playbook -v -f1 playbooks/bootstrap/site.yaml --limit bastion"