Description of problem:
The stop l3 agent connectivity check is failing with micro percentage of packet loss 0.00792142%
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. deploy osp16.1 GA
2. update the undercloud to latest version
3. update the overcloud
4. run l3 agent connectivity check
0 percent of packet loss
so the packet loss is actual 1 sent ping got lost. As the #29 jobs has the same puddle than job #28 and job #28 was successful, I think this is just a random lost ping.
If that kind of error happen too often, we may then add something in tripleo-upgrade in order to not get this kind of false positive: maybe a test on the ping count, if < 5 then not fail.
Lowering the priority and severity, waiting until next run, if we get that 1 ping loss again before moving on tripleo-upgrade patch.
Does not seem to reproduce.