tripleo-upgrade ping test may report false negative.
Bug #1919323 reported by
Sofer Athlan-Guyot
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tripleo |
Triaged
|
High
|
Sofer Athlan-Guyot | ||
Bug Description
Hi,
from time to time the ping test report failure with "1 packet loss".
This is a false negative and is due to the fact that we end the ping test by a sigterm which isn't handled in any way by the ping utility[1].
We need either
1. to better handle the termination of the ping command
2. ignore failure when we have exactly "1 packet loss".
1 seems hard to handle correctly and 2 should be enough, ie it won't hide true error[2]
[1] https:/
[2] that's really a "personal" assumption based on experience.
| summary: |
- tripleo-upgrade ping test may report false positive. + tripleo-upgrade ping test may report false negative. |
| description: | updated |
| Changed in tripleo: | |
| milestone: | wallaby-3 → wallaby-rc1 |
| Changed in tripleo: | |
| milestone: | wallaby-rc1 → xena-1 |
| Changed in tripleo: | |
| milestone: | xena-1 → xena-2 |
| Changed in tripleo: | |
| milestone: | xena-2 → xena-3 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/tripleo-upgrade 8.0.0 | #1 |
To post a comment you must log in.
This issue was fixed in the openstack/