yahoo-eng-team team mailing list archive

[OpenStack Infra <1524908@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/255989
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=521e1c9face737a8d432be16ad63829aaf21384e
Submitter: Jenkins
Branch:    master

commit 521e1c9face737a8d432be16ad63829aaf21384e
Author: Oleg Bondarev <obondarev@xxxxxxxxxxxx>
Date:   Thu Dec 10 19:49:25 2015 +0300

    Do not remove router from dvr_snat agents on dvr port deletion
    
    When dvr serviceable port is deleted/migrated, dvr callback checks
    if there are any more dvr serviceable ports on the host and if
    there are no - removes the router from the agent on that host.
    To prevent snat namespace removal we need to check SNAT bindings
    and not remove router from l3 agent hosting SNAT.
    
    Closes-Bug: #1524908
    Change-Id: I8c76bccdf495702e4c550df2eadec93c63e32120


** Changed in: neutron
       Status: In Progress => 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/1524908

Title:
  Router may be removed from dvr_snat agent by accident

Status in neutron:
  Fix Released

Bug description:
  This popped up during https://review.openstack.org/#/c/238478
   - when dvr serviceable port is deleted/migrated, dvr callback checks if there are any more dvr serviceable ports on the host and if there are no - removes the router from the agent on that host
   - in case dhcp port is deleted/migrated this may lead to router being deleted from dvr_snat agent, which includes snat namespace deletion

  Need to check agent mode and only remove router from dvr agents
  running on compute nodes in this case.

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