neutron

  1. Bug #1585165
  2. Comment #11

Comment 11 for bug 1585165

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/liberty)

Reviewed: https://review.openstack.org/329107
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=a6e020cc199df0eafe7b4fdcd92fa74881d27dfa
Submitter: Jenkins
Branch: stable/liberty

commit a6e020cc199df0eafe7b4fdcd92fa74881d27dfa
Author: rossella <email address hidden>
Date: Wed Jun 8 17:18:51 2016 +0200

    After a migration clean up the floating ip on the source host

    When a VM is migrated that has a floating IP associated, the L3
    agent on the source host should be notified when the migration
    is over. If the router on the source host is not going to be
    removed (there are other ports using it) then we should nofity
    that the floating IP needs to be cleaned up.

    Closes-bug: #1585165
    (cherry picked from commit a1f06fd707ffe663e09f2675316257c8dc528d47)

    Conflicts:
     neutron/db/l3_dvrscheduler_db.py
     neutron/tests/unit/scheduler/test_l3_agent_scheduler.py
    Change-Id: Iad6fbad06cdd33380ef536e6360fd90375ed380d