Bug 1887148
Summary: | [updates] 16.1, 0.08 packet loss on stop l3 agent connectivity check test | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Ronnie Rasouli <rrasouli> |
Component: | openstack-tripleo-heat-templates | Assignee: | Sofer Athlan-Guyot <sathlang> |
Status: | CLOSED WORKSFORME | QA Contact: | David Rosenfeld <drosenfe> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 16.1 (Train) | CC: | jstransk, mbollo, mburns |
Target Milestone: | --- | Keywords: | Regression, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-10-19 13:22:16 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ronnie Rasouli
2020-10-11 09:36:53 UTC
Hi, 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. |