Description of problem: Version-Release number of selected component (if applicable): python-neutronclient-2.3.9-1.el7ost.noarch openstack-neutron-2014.2.1-6.el7ost.noarch openstack-neutron-ml2-2014.2.1-6.el7ost.noarch python-neutron-2014.2.1-6.el7ost.noarch openstack-neutron-openvswitch-2014.2.1-6.el7ost.noarch How reproducible: 100% Steps to Reproduce: 1.Create a distributed router #neutron router-create router1 2. Set the router gateway #neutron router-gateway-set router1 public1 3. Verify the dvr_snat agent exists in: #neutron l3-agent-list-hosting-router router1 4. Remove the router from the agent: #neutron l3-agent-router-remove <agent-id> router1 5. Add the router to the agent #neutron l3-agent-router-add <agent-id> router1 Actual results: Not Found (HTTP 404) (Request-ID: req-135efd0d-f2ed-4c98-b3ae-507eec9fe3de) Expected results: The router should be added to the agent Additional info:
Attaching the relevant patch (currently in review) and linking to the tracker bug.
https://review.openstack.org/#/c/123815 was abandoned. Instead, there are couple of fixes that were merged: https://review.openstack.org/#/c/118491/ https://review.openstack.org/#/c/122024/
A Comment by Oleg Bondarev that seems to be important: L3 agent support for snat rescheduling is added in https://review.openstack.org/#/c/211939/ (originally in https://review.openstack.org/#/c/199514 but then moved to a separate patch).
Fixed in upstream Liberty branch and there's no reason to backport it. No further action is required.