fix(metallb): retry transient apiserver resets in config tests
- The Layer 2 and BGP final configuration checks ran a kubectl get per resource with no retry, so a transient connection refused from the kube API could abort converge - Mirror the download_retries/download_delay retry pattern used by the 'Wait for MetalLB resources' task so these checks survive api server resets on slow runners
This commit is contained in:
parent
d1d82b9373
commit
a4f6c899e3
|
|
@ -118,6 +118,10 @@
|
|||
changed_when: false
|
||||
run_once: true
|
||||
when: metal_lb_mode == "layer2"
|
||||
register: metallb_l2_test_result
|
||||
until: metallb_l2_test_result.rc == 0
|
||||
retries: "{{ download_retries }}"
|
||||
delay: "{{ download_delay }}"
|
||||
with_items:
|
||||
- IPAddressPool
|
||||
- L2Advertisement
|
||||
|
|
@ -128,6 +132,10 @@
|
|||
changed_when: false
|
||||
run_once: true
|
||||
when: metal_lb_mode == "bgp"
|
||||
register: metallb_bgp_test_result
|
||||
until: metallb_bgp_test_result.rc == 0
|
||||
retries: "{{ download_retries }}"
|
||||
delay: "{{ download_delay }}"
|
||||
with_items:
|
||||
- IPAddressPool
|
||||
- BGPPeer
|
||||
|
|
|
|||
Loading…
Reference in New Issue