neutron

Floating IP is not removed when VM is terminated in midonet plugin

Bug #1231913 reported by Ryu Ishimoto
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Dave Cahill
neutron 2013.2 "havana"

Bug Description

In Midonet plugin, when a VM terminates, floating IP does not get diassociated properly. This left the floating IP associated with a terminated instance and required you to explicitly diassociate in a separate step. This also left MidoNet resources dangling around when the VM terminates.

Tags: midonet
Dave Cahill (dcahill-f)
Changed in neutron:
assignee: nobody → Dave Cahill (dcahill-f)
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/48623

Changed in neutron:
status: New → In Progress
Mark McClain (markmcclain)
tags: added: havana-rc-potential midonet
Changed in neutron:
importance: Undecided → Medium
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (master)

Reviewed: https://review.openstack.org/48623
Committed: http://github.com/openstack/neutron/commit/f4b78c7f17e29448ed54b136eeb4ac700b324120
Submitter: Jenkins
Branch: master

commit f4b78c7f17e29448ed54b136eeb4ac700b324120
Author: Dave Cahill <email address hidden>
Date: Fri Sep 27 10:44:00 2013 +0000

    Disassociate floating IPs from port on terminate

    Bugfix - floating IPs were left associated after VM
    was terminated. Now call disassociate_floatingips
    within delete_port as in other networking plugins.

    Add L3NatDBIntTestCase suite to cover the
    floating IP disassociation case, and fix all failing
    tests from that suite.

    Change-Id: I856c46631e495d513065fc9e987898408441a21e
    Closes-Bug: #1231913

Changed in neutron:
status: In Progress → Fix Committed
Mark McClain (markmcclain)
Changed in neutron:
milestone: none → havana-rc2
tags: removed: havana-rc-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to neutron (milestone-proposed)

Fix proposed to branch: milestone-proposed
Review: https://review.openstack.org/50662

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (milestone-proposed)

Reviewed: https://review.openstack.org/50662
Committed: http://github.com/openstack/neutron/commit/cd8c8b367f7df75337438b10e1a1c0f6d5031810
Submitter: Jenkins
Branch: milestone-proposed

commit cd8c8b367f7df75337438b10e1a1c0f6d5031810
Author: Dave Cahill <email address hidden>
Date: Fri Sep 27 10:44:00 2013 +0000

    Disassociate floating IPs from port on terminate

    Bugfix - floating IPs were left associated after VM
    was terminated. Now call disassociate_floatingips
    within delete_port as in other networking plugins.

    Add L3NatDBIntTestCase suite to cover the
    floating IP disassociation case, and fix all failing
    tests from that suite.

    Change-Id: I856c46631e495d513065fc9e987898408441a21e
    Closes-Bug: #1231913
    (cherry picked from commit f4b78c7f17e29448ed54b136eeb4ac700b324120)

Changed in neutron:
status: Fix Committed → Fix Released
Thierry Carrez (ttx)
Changed in neutron:
milestone: havana-rc2 → 2013.2
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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