yahoo-eng-team team mailing list archive

[OpenStack Infra <1231913@xxxxxxxxxxxxxxxxxx>]

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

commit cd8c8b367f7df75337438b10e1a1c0f6d5031810
Author: Dave Cahill <dcahill@xxxxxxxxxxxx>
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

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1231913

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

Status in OpenStack Neutron (virtual network service):
  Fix Released

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1231913/+subscriptions