Quantum Linux Bridge interface driver plug operation fails with RTNETLINK error

Bug #1000580 reported by Sumit Naiksatam
28
This bug affects 4 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Fix Released
Undecided
Sumit Naiksatam
neutron
Fix Released
High
Sumit Naiksatam

Bug Description

This is happening when the gateway initialization code is called a second time. The plug operation tries to set the IP address on the bridge which already has an IP address. Ideally the IP address should not be set for an existing bridge device (check for an existing device is being performed but the IP address is being set outside the check).

Changed in nova:
assignee: nobody → Sumit Naiksatam (snaiksat)
status: New → In Progress
Changed in quantum:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Sumit Naiksatam (snaiksat)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (master)

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

Changed in quantum:
milestone: none → folsom-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to nova (master)

Reviewed: https://review.openstack.org/7567
Committed: http://github.com/openstack/nova/commit/7e845f4af6f89253d9c47645875aa67ef24ebee3
Submitter: Jenkins
Branch: master

commit 7e845f4af6f89253d9c47645875aa67ef24ebee3
Author: Sumit Naiksatam <email address hidden>
Date: Thu May 17 16:14:52 2012 -0700

    Fix for Quantum LinuxBridge Intf driver plug call

    The current implementation of the plug operation tries to assign an IP
    address to a bridge even if it already has one. The fix is to do this
    only when a new device is created. The check for a new device was
    already being performed however the IP address was being set outside
    that check. That's being corrected here, minor fix.

    bug 1000580

    Change-Id: I45215a3ca87a32ef4c2a2f76bab9b743eabb525e

Changed in nova:
status: In Progress → Fix Committed
Changed in quantum:
status: In Progress → Fix Committed
Thierry Carrez (ttx)
Changed in quantum:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in nova:
milestone: none → folsom-1
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to nova (stable/essex)

Fix proposed to branch: stable/essex
Review: https://review.openstack.org/8647

Revision history for this message
Mark McLoughlin (markmc) wrote :

A comment in https://review.openstack.org/#/c/8647/ suggests this isn't a bug in Essex. Can anyone confirm either way?

Revision history for this message
Sumit Naiksatam (snaiksat) wrote :

The patch which which seems to have introduced this issue is: https://bugs.launchpad.net/nova/+bug/983024, and that has been tagged as an essex-backport. If that code does get backported, we will see this issue in Essex.

Mark McLoughlin (markmc)
no longer affects: nova/essex
Revision history for this message
Mark McLoughlin (markmc) wrote :

bug #1042249 suggests this is an issue with 2012.1.2

Thierry Carrez (ttx)
Changed in quantum:
milestone: folsom-1 → 2012.2
Thierry Carrez (ttx)
Changed in nova:
milestone: folsom-1 → 2012.2
Revision history for this message
Aimon Bustardo (aimonb) wrote :

Is anyone else seeing this in Grizzly?

Sean Dague (sdague)
no longer affects: nova/essex
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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