Improve connectivity check
Currently, the ICMP check can fail if the network
configuration takes too long. This can fail the
overall deployment, but the network configuration
can still be successful. This change broadens the
scope of the connectivity check by increasing the
number of IMCMP requests sent each time. To make
it more flexibile and allowing for situations where
interfaces take a little longer to become active.
Resolves: rhbz#2053404
Change-Id: I9eac272df3a99c6869c752ae779d52848a9ad78f
(cherry picked from commit 3708fce565
)
This commit is contained in:
parent
f9786b152c
commit
1635466f7b
@ -31,10 +31,12 @@
|
||||
- name: Network availability validation block
|
||||
block:
|
||||
- name: Check IP responsiveness
|
||||
command: "{{ _ping_cmd }} -w 10 -c 1 {{ controller }}"
|
||||
command: "{{ _ping_cmd }} -w 10 -c 5 {{ controller }}"
|
||||
retries: 10
|
||||
delay: 60
|
||||
changed_when: false
|
||||
register: ping_result
|
||||
until: ping_result.rc == 0
|
||||
|
||||
- name: Validate packet with {{ _mtu }} MTU size can reach controller from {{ _nic }}
|
||||
command: "{{ _ping_cmd }} -w 10 -s {{ _mtu }} -c 1 {{ controller }}"
|
||||
|
Loading…
Reference in New Issue
Block a user