-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
2
-
False
-
-
False
-
?
-
?
-
?
-
?
-
None
-
-
-
Neutron Sprint 4
-
1
-
Important
Hi,
In all successful periodic-internal-adoption-multinode-to-crc-no-ceph jobs we can see a cut in pings test for around 40sec.
One example of such cut can be seen in ping_results-hr.txt from that build.
Currently that doesn't fails the jobs as we have very high thresholds. We want to lower them in Ping test thresholds for adoption are set too high and need adjustment.
So, is that cut unavoidable and should be included in the threshold as acceptable or should it be fixed and have a 0 ping loss goal ?
Regards,
- blocks
-
OSPRH-8158 Add continuous ping test into Adoption test suite
- Closed
- is triggering
-
OSPRH-12313 Root cause and Refine OSPRH-12246
- Closed