bigswitch multi-tenant floating IP loss

Bug #1262488 reported by Kevin Benton
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Undecided
Kevin Benton

Bug Description

The bigswitch plugin fails to use the admin context to update the floating IPs on the backend controller.
When one tenant assigns a floating IP, the update to the controller doesn't contain the floating IPs of the other tenants so the controller thinks they have been removed.

Changed in neutron:
assignee: nobody → Kevin Benton (blak111)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (master)

Fix proposed to branch: master
Review: https://review.openstack.org/63047

Changed in neutron:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/63047
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=5abac020f459045ceee75c971e179d9dbce8eac8
Submitter: Jenkins
Branch: master

commit 5abac020f459045ceee75c971e179d9dbce8eac8
Author: Kevin Benton <email address hidden>
Date: Thu Dec 19 03:52:20 2013 +0000

    BigSwitch: Fixes floating IP backend updates

    Changes BigSwitch plugin to correctly use
    admin context on floating IP updates to the
    backend controller so they correctly contain
    floating IPs for all tenants.

    Closes-Bug: #1262488
    Change-Id: I6f2666c242e6d9b0684943db073a2284d01fa1e0

Changed in neutron:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in neutron:
milestone: none → icehouse-2
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: icehouse-2 → 2014.1
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.