From 07975eb7e9a31a964feb86dc39d2dfd548084759 Mon Sep 17 00:00:00 2001 From: Adam Williamson Date: Sat, 9 Sep 2017 11:40:23 -0700 Subject: [PATCH] openqa tap: handle eth2 in the custom firewall rules too Signed-off-by: Adam Williamson --- inventory/group_vars/openqa-tap-workers | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/inventory/group_vars/openqa-tap-workers b/inventory/group_vars/openqa-tap-workers index 3fd28770b7..571b6a62c4 100644 --- a/inventory/group_vars/openqa-tap-workers +++ b/inventory/group_vars/openqa-tap-workers @@ -5,14 +5,16 @@ openqa_tap: true host_group: openqa-tap-workers # firewall rules to allow openQA openvswitch guests to communicate +# eth0 for x86_64 worker hosts, eth2 for ppc64 worker host custom_rules: [ '-A FORWARD -i br0 -j ACCEPT', '-A FORWARD -m state -i eth0 -o br0 --state RELATED,ESTABLISHED -j ACCEPT', + '-A FORWARD -m state -i eth2 -o br0 --state RELATED,ESTABLISHED -j ACCEPT', '-A INPUT -i br0 -j ACCEPT' ] # we do stuff with ifcfg that base doesn't understand. terrible, terrible # stuff. seriously - it doesn't handle the openvswitch config well. so -# let's tell it to just configure eth0 for us and leave everything else -# alone. -ansible_ifcfg_whitelist: ['eth0'] +# let's tell it to just configure eth0 (and eth2, for ppc64) for us and +# leave everything else alone. +ansible_ifcfg_whitelist: ['eth0', 'eth2']