icmp_seq=1 Destination unreachable: Address unreachable causing built failures on fortnebula nodes
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack-Gate |
New
|
Undecided
|
Donny Davis | ||
Bug Description
Seen here:
}
2019-12-17 19:07:10.885 | localhost | SUCCESS | network_
mirror.
2019-12-17 19:07:11.086 | 192.168.48.65 | SUCCESS | network_
mirror.
2019-12-17 19:07:11.459 | localhost | SUCCESS | network_
http://
2019-12-17 19:07:11.907 | 192.168.48.65 | SUCCESS | network_
http://
2019-12-17 19:07:13.366 | localhost | FAILED | network_
PING mirror.
From 2001:470:
--
Looks like it's mostly fortnebula nodes:
The grenade jobs here are using devstack-gate. I don't know if there is something different about how the host network setup ping check works in d-g than the zuulv3 native jobs but maybe something to adjust in d-g.
| Donny Davis (donny-g) wrote | #1 |
| Changed in openstack-gate: | |
| assignee: | nobody → Donny Davis (donny-g) |
This issue on fortnebula was determined to be a bad set of static routes for test node network to mirror node network communications.
Static routes are used for more direct access from tenant to tenant. A system update forced FN to have to recreate the external gateways for each tenant router, but the static routes were never updated to reflect the new path.