Change:
${BRIDGE_BASE}.0.0/16 dev ${DOCKER_BRIDGE} scope link src ${BRIDGE_ADDRESS} EOF # generate the post-configure script to be called by salt as cmd.wait cat <<EOF > ${POST_NETWORK_SCRIPT} #!/bin/bash set -e <del> # NAT interface fails to revive on network restart, so OR-gate to true systemctl restart network.service || true # set docker bridge up, and set stp on the ovs bridge ip link set dev ${DOCKER_BRIDGE} up ovs-vsctl set Bridge ${OVS_SWITCH} stp_enable=true </del> <ins> # Only do this operation once, otherwise, we get docker.servicee files output on disk, and the command line arguments get applied multiple times grep -q kbr0 /etc/sysconfig/docker || { # Stop docker before making these updates systemctl stop docker # NAT interface fails to revive on network restart, so OR-gate to true systemctl restart network.service || true # set docker bridge up, and set stp on the ovs bridge ip link set dev ${DOCKER_BRIDGE} up ovs-vsctl set Bridge ${OVS_SWITCH} stp_enable=true </ins> <del> # modify the docker service file such that it uses the kube docker bridge and not its own sed -ie "s/ExecStart=/usr/bin/docker -d/ExecStart=/usr/bin/docker -d -b=${DOCKER_BRIDGE} --iptables=false/g" /usr/lib/systemd/system/docker.service systemctl daemon-reload systemctl restart docker.service </del> <ins> # modify the docker service file such that it uses the kube docker bridge and not its own #echo "OPTIONS=-b=kbr0 --iptables=false --selinux-enabled" > /etc/sysconfig/docker echo "OPTIONS='-b=kbr0 --iptables=false --selinux-enabled'" >/etc/sysconfig/docker systemctl daemon-reload systemctl restart docker.service </ins> <del> # setup iptables masquerade rules so the pods can reach the internet iptables -t nat -A POSTROUTING -s ${BRIDGE_BASE}.0.0/16 ! -d ${BRIDGE_BASE}.0.0/16 -j MASQUERADE </del> <ins> # setup iptables masquerade rules so the pods can reach the internet iptables -t nat -A POSTROUTING -s ${BRIDGE_BASE}.0.0/16 ! -d ${BRIDGE_BASE}.0.0/16 -j MASQUERADE </ins> <del> # persist please iptables-save >& /etc/sysconfig/iptables </del> <ins> # persist please iptables-save >& /etc/sysconfig/iptables } </ins> EOF chmod +x ${POST_NETWORK_SCRIPT}

Discussion:
Which jobs are failing: capa-conformance-v1alpha3-k8s-master (ci-cluster-api-provider-aws-make-conformance-v1alpha3-k8s-ci-artifacts) Which test(s) are failing: [] Pods should get a host IP [NodeConformance] [Conformance] Since when has it been failing: 06-06 17:23 PDT Testgrid link: Reason for failure: <*errors.errorString | 0xc0000daf10: { s: "pod ran to completion", } pod ran to completion occurred skipped 89 lines unfold_more Jun 6 10:07:34.676: INFO: Latency metrics for node ip-10-0-0- Jun 6 10:07:34.676: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "pods-7990" for this suite. Anything else we need to know: /sig testing /cc /priority critical-urgent /milestone v1.19
/sig scheduling observing a timeout Jun 10 05:42:34.202: INFO: found a healthy node: test1-md-0-4qcf5 [It] runs ReplicaSets to verify preemption running path [Conformance] Jun 10 05:42:42.675: INFO: pods created so far: [1 1 1] Jun 10 05:42:42.675: INFO: length of pods created so far: 3 Jun 10 05:44:42.765: FAIL: pod sched-preemption-path-3834/pod4 failed to preempt other pods Unexpected error: &lt;*errors.errorString | 0xc00011bdd0: { s: "timed out waiting for the condition", } timed out waiting for the condition occurred Full Stack Trace (0xc000e48f20, 0xc001dbb800, 0x1bf08eb000) +0x16b skipped 318 lines unfold_more Jun 10 05:44:44.847: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready STEP: Destroying namespace "sched-preemption-4796" for this suite.

[AfterEach] [sig-scheduling] SchedulerPreemption [Serial]
/remove-sig scheduling I observing failure since yesterday as the cluster failed to get created using the CloudFormation template Attempting to create CloudFormation stack cluster-api-provider-aws-sigs-k8s-io Error: failed to create AWS CloudFormation stack: ResourceNotReady: failed waiting for successful resource stateError: failed to create AWS CloudFormation stack: ResourceNotReady: failed waiting for successful resource state
The label(s) cannot be applied, because the repository doesn't have them <detailsIn response to : /sig remove scheduling Error: failed to create AWS CloudFormation stack: ResourceNotReady: failed waiting for successful resource stateError: failed to create AWS CloudFormation stack: ResourceNotReady: failed waiting for successful resource state` Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/remove-sig scheduling
/assign
/remove-sig testing SIG testing doesn't own CAPA bringup failures
/sig cluster-lifecycle
It is expected that will provide a fix /cc
/assign
/lifecycle active