Reviewed: https://review.openstack.org/340659 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=bd076a09833275c388c8feb9abf4f7f4278290d8 Submitter: Jenkins Branch: master
commit bd076a09833275c388c8feb9abf4f7f4278290d8 Author: Kevin Benton <[email protected]> Date: Mon Jul 11 06:14:24 2016 -0700 Rollback router intf port update if csnat update fails If a CSNAT port update fails when a subnet is added, it will leave the regular updated router port in the changed state since it's a separate port update with a separate transaction. So when the CSNAT update fails we need explicitly undo the 1st update with another update. Closes-Bug: #1609693 Change-Id: If979aebbebf6da77f3fcec0cc7ec8b27e388aba4 ** 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/1609693 Title: csnat port update failure does not undo port update Status in neutron: Fix Released Bug description: With DVR an IPv6 subnet being added to an interface will also add the subnet to the CSNAT port. If adding the subnet to CSNAT fails (either with a retriable error or a regular exception), the change to the original router port will not be undone. This leads to inconsistency between the two and results in errors like: Details: {u'message': u'Bad router request: Router already has a port on subnet 703ab4e2-8ce8-42b2-a5b8-436f9f9088b4.', u'detail': u'', u'type': u'BadRequest'} http://logs.openstack.org/53/350253/1/gate/gate-tempest-dsvm-neutron-dvr/f5df583/logs/testr_results.html.gz To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1609693/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
