Created attachment 1792517 [details]
example

Description of problem:
I booted 3 master 3 workers and simulated
no latency in master-0 (192.168.127.10)
network latency in master-1 (192.168.127.11)
packet loss in master-2 (192.168.127.12)

workers with no latency (192.168.127.13-192.168.127.15)

master-1 validation is:
sufficient-network-latency-requirement-for-role: Error while attempting to validate network latency: host with IP 192.168.127.12 not found in inventory.
sufficient-packet-loss-requirement-for-role: Error while attempting to validate packet loss validation: host with IP 192.168.127.14 not found in inventory.

The issue is that 192.168.127.14 is a worker node ip
In addition, worker-0 fails network validations although no latency in worker nodes - validation contain master ip::
sufficient-packet-loss-requirement-for-role: Error while attempting to validate packet loss validation: host with IP 192.168.127.11 not found in inventory.

network latency is calculated per role, therefore i expect no validation failures between workers and masters


Version-Release number of selected component (if applicable):
Staging v1.0.22.1

How reproducible:
100%

Steps to Reproduce:
1. boot 3 masters 3 worker, set roles and api & ingress vip
2. set network latency in master-1, and packet loss in master-2 
sudo tc qdisc add dev ens3 root netem delay 150ms
sudo tc qdisc add dev ens3 root netem loss 10%

3. wait for network latency validation failures 

Actual results:
masters with latency got wrong worker IP in validation message
workers with no latency got validation failures containing masters ip

Expected results:
masters with latency got correct worker IP in validation message
workers with no latency got no validation failures

Additional info: