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
MOS Maintenance
Won't Fix
MOS Neutron
Won't Fix
MOS Maintenance
MOS Maintenance

Bug Description

MOS 7.0 MU-6
Associating/disassociating FIPs to VMs port leaves old fg- devices in fip-namespace.
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 :

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.

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)

Fix proposed to branch: openstack-ci/fuel-7.0/2015.1.0
Change author: Rodion Tikunov <email address hidden>

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)

Submitter: Denis V. Meltsaykin <email address hidden>
Branch: openstack-ci/fuel-7.0/2015.1.0

Commit: 8005753cf07afb1431f269f2c7ce034c7ba6650c
Author: Rodion Tikunov <email address hidden>
Date: Wed Nov 16 09:17:50 2016

Revert "DVR: Pings to floatingip returns with fixed-ip on same network"

This reverts commit 2d4cfe1908e7351d8897a7c9841ee379703afa79.

Change-Id: I512c10dc6a0eceb7c5088d01bb4f861e07825c6e
Closes-bug: #1641762

Revision history for this message
Rodion Tikunov (rtikunov) wrote :
Revision history for this message
Denis Meltsaykin (dmeltsaykin) wrote :

Won't Fix for 8.0 and 7.0 since they are out of support.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.