Correctly delete openstack_networking_router_interface_v2 resources #1297
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When creating multiple
openstack_networking_router_interface_v2
resources for different IPv6 subnets in the same network, openstack will
attach these to the same port on the router.
On destroy the current implementation will pass the
port_id
torouters.RemoveInterface
, which will trigger the deletion of the wholeport, including other
openstack_networking_router_interface_v2
resourceson the same port.
This commit changes this behaviour (so that only the correct router interface
gets deleted) and adds a test case that ensures this does not break
again in the future.
Note: We were affected by this bug. In our case we deleted an
openstack_networking_router_interface_v2
viaterraform destroy -target …
, but terraform-provider-openstack silently deleted the whole port including another, importantopenstack_networking_router_interface_v2
resource which was crucial for our production setup.