Delete router broken for NSX-mh
Bug #1426570 reported by
Salvatore Orlando
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vmware-nsx |
Fix Released
|
High
|
Salvatore Orlando |
Bug Description
Starting with 1e00041b0bcb831
While this change has been beneficial for many plugins, it did not work for NSX-mh.
Indeed the NSX-mh removes the logical router from the backend before moving on to the database operation.
As the database operation now attempts to operate on the backend object, this fails because the object has been deleted in the meanwhile.
Changed in vmware-nsx: | |
status: | New → In Progress |
Changed in vmware-nsx: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/159653 /git.openstack. org/cgit/ stackforge/ vmware- nsx/commit/ ?id=2f46cd7afdd 002a0d139896df3 952939d4c83ca0
Committed: https:/
Submitter: Jenkins
Branch: master
commit 2f46cd7afdd002a 0d139896df39529 39d4c83ca0
Author: Salvatore Orlando <email address hidden>
Date: Thu Feb 26 14:58:45 2015 -0800
Do not attempt ext gw port reset for deleted routers
This patch prevents _nsx_delete_ ext_gw_ port from attempting to 75760eb6347bb3e ae55649328
operate on the external gateway port for a router which has
already been deleted from the backend.
This situation occurs since the behaviour of delete_router
has been changed by 1e00041b0bcb831
Closes-Bug: #1426570
Change-Id: I2029df5227e312 815fa3f955bfd1b cc19c5216b5