Set ansible_ifcfg_whitelist on aarch64-02 and aarch64-03 for now

There is a connected eth2 on each of these machines but no
eth2_ip or eth2_nm in these files, which breaks the 'copy ifcfg
files - non virthost' play. For now I'm just going to set this
whitelist var which should tell ansible to ignore eth2, we can
change the approach later if we want to.

Signed-off-by: Adam Williamson <awilliam@redhat.com>
This commit is contained in:
Adam Williamson 2020-03-03 11:01:25 -08:00 committed by Pierre-Yves Chibon
parent 6423bf52a2
commit 4b9dc6585c
2 changed files with 8 additions and 0 deletions

View file

@ -14,6 +14,10 @@ nrpe_procs_crit: 300
sudoers: "{{ private }}/files/sudo/qavirt-sudoers"
# we seem to have an eth2 plugged in that isn't configured here,
# which breaks "copy ifcfg files - non virthost" role
ansible_ifcfg_whitelist: ['eth0', 'eth1']
# this is a powerful machine, can handle more openQA workers
openqa_workers: 8
# firewall ports for server->worker websockets connections

View file

@ -14,6 +14,10 @@ nrpe_procs_crit: 300
sudoers: "{{ private }}/files/sudo/qavirt-sudoers"
# we seem to have an eth2 plugged in that isn't configured here,
# which breaks "copy ifcfg files - non virthost" role
ansible_ifcfg_whitelist: ['eth0', 'eth1']
# this is a powerful machine, can handle more openQA workers
openqa_workers: 8
# firewall ports for server->worker websockets connections