Skip to content

Commit

Permalink
Update coreos-calico-aio scenario to test no group vars (#2314)
Browse files Browse the repository at this point in the history
This updated scenario ensures deployment still passes without
having any group_vars available.
  • Loading branch information
mattymo authored Feb 12, 2018
1 parent f4a68ea commit 5903aea
Show file tree
Hide file tree
Showing 2 changed files with 9 additions and 0 deletions.
8 changes: 8 additions & 0 deletions tests/cloud_playbooks/create-gce.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@
mode: default
preemptible: no
ci_job_name: "{{ lookup('env', 'CI_JOB_NAME') }}"
delete_group_vars: no
tasks:
- name: include vars for test {{ ci_job_name }}
include_vars: "../files/{{ ci_job_name }}.yml"
Expand Down Expand Up @@ -64,6 +65,13 @@
dest: "{{ inventory_path|dirname }}/group_vars/fake_hosts.yml"
when: mode in ['scale', 'separate-scale', 'ha-scale']

- name: Delete group_vars directory
file:
path: "{{ inventory_path|dirname }}/group_vars"
state: absent
recurse: yes
when: delete_group_vars

- name: Wait for instances
hosts: "waitfor_hosts"
gather_facts: false
Expand Down
1 change: 1 addition & 0 deletions tests/files/coreos-calico-aio.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@ mode: aio
startup_script: 'systemctl disable locksmithd && systemctl stop locksmithd'

# Deployment settings
no_group_vars: true
bootstrap_os: coreos
kube_network_plugin: calico
resolvconf_mode: host_resolvconf # this is required as long as the coreos stable channel uses docker < 1.12
Expand Down

0 comments on commit 5903aea

Please sign in to comment.