Neutron DVR L3 agent doesn't cleanup fip-namespace from old fg devices
Bug #1641762 reported by
Eugene Nikanorov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mirantis OpenStack |
Invalid
|
High
|
MOS Maintenance | ||
| 7.0.x |
Won't Fix
|
Critical
|
MOS Neutron | ||
| 8.0.x |
Won't Fix
|
High
|
MOS Maintenance | ||
| 9.x |
Invalid
|
High
|
MOS Maintenance | ||
Bug Description
MOS 7.0 MU-6
Associating/
That prevents from reusing FIP address properly and prevents it from actually working. Some times L3 agent assigns flaoting ip to a wrong fg- devices, sometimes it fails to assing it. Sometimes it fails to delete address from stale fg- device.
Easily reproducible.
| no longer affects: | mos/8.0.x |
Revision history for this message
| Eugene Nikanorov (enikanorov) wrote | #1 |
| description: | updated |
Revision history for this message
| Fuel Devops McRobotson (fuel-devops-robot) wrote Fix proposed to openstack/neutron (openstack-ci/fuel-7.0/2015.1.0) | #2 |
Revision history for this message
| Fuel Devops McRobotson (fuel-devops-robot) wrote Fix merged to openstack/neutron (openstack-ci/fuel-7.0/2015.1.0) | #3 |
Revision history for this message
| Rodion Tikunov (rtikunov) wrote | #4 |
Revision history for this message
| Denis Meltsaykin (dmeltsaykin) wrote | #5 |
To post a comment you must log in.
It looks like if the last fip is being deleted from the compute node,
fg-device is not deleted.
Later after fip is associated, old fg- device might be used in some cases.
Looks like L3 agent works with its cache incorrectly.
It takes L3 agent restart to cleanup the cache, but the namespace is not cleaned up automatically.