Monitoring of DVR-related fip/qrouter namespace veth pairs
Bug #1919931 reported by
Paul Goins
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Neutron Open vSwitch Charm |
New
|
Undecided
|
Unassigned | ||
| charm-openstack-service-checks |
Won't Fix
|
Undecided
|
Unassigned | ||
Bug Description
In response to a recent customer issue, it's been suggested that we add some sort or check which allows us to detect when DVR routing is broken. Specifically, this is in response to this bug: https:/
When this bug occurs, the veth pairs between the fip and qrouter namespaces may get inadvertently removed, resulting in the fip namespace being unable to forward traffic to the qrouter namespace, thus effectively floating IPs break for instances on hosts where this occurs.
It's been suggested that we add some sort of alert so we can see if the veth links between the qrouter and fip namespaces are missing, so as to indicate a problem with DVR health.
Revision history for this message
| Paul Goins (vultaire) wrote | #1 |
Revision history for this message
| Eric Chen (eric-chen) wrote | #2 |
| Changed in charm-openstack-service-checks: | |
| status: | New → Won't Fix |
To post a comment you must log in.
Added the neutron-openvswitch charm. This type of a check would probably need to be checked directly on each node which could host such qrouter/fip namespaces, so it seems more appropriate.