l3 code can leave orphaned ports
Bug #1600344 reported by
Kevin Benton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Undecided
|
Kevin Benton |
Bug Description
The L3 code creates ports and then RouterPort records for those ports in a separate transaction. If the server encounters an exception when creating the RouterPort records (e.g. lost connection to database, router was concurrently deleted, etc), the port will remain but will not have a RouterPort so it won't be able to be deleted.
Changed in neutron: | |
assignee: | nobody → Kevin Benton (kevinbenton) |
Changed in neutron: | |
status: | New → In Progress |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/333809 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=fbd3578d649 4fa3f08d7568678 3f31454b1b42e5
Committed: https:/
Submitter: Jenkins
Branch: master
commit fbd3578d6494fa3 f08d75686783f31 454b1b42e5
Author: Kevin Benton <email address hidden>
Date: Wed Jun 22 18:23:19 2016 -0700
Delete gw port on exceptions
Clean up related core plugin ports on routers when there is a failure
creating the record for the router port.
The two partial bugs will be fixed after ee763cc4be6d679 fe9f501eb3a19b5 has merged.
I476d3e03c8
Closes-Bug: #1600344 ee090ebab921f0d eea533b6fc8
Partial-Bug: #1535225
Partial-Bug: #1535226
Change-Id: I8dd832f35e20d1