Instance remains active after deletion in case was created on other tenant's network
Bug #1238129 reported by
Evgeny Fedoruk
This bug report is a duplicate of:
Bug #1246258: UnboundLocalError: local variable 'network_name' referenced before assignment.
Edit
Remove
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nova |
New
|
Undecided
|
Evgeny Fedoruk |
Bug Description
Tenant A has a private network named A-private-net-1
Admin creates a new instance, connected to A-private-net-1 for tenant B
Trying deleting the instance gives no error but instance remains alive.
The problem is that instance's network port (which connected to other tenant's private network) deletion fails.
The WA is to first delete the port and then delete the instance.
The bug is also affecting following scenario:
1. Instance is up and running.
2. Shut off instance. Instance is shutting down.
3. Start the instance. Instance is NOT starting.
Changed in neutron: | |
assignee: | nobody → Evgeny Fedoruk (evgenyf) |
affects: | neutron → nova-project |
tags: | added: network |
description: | updated |
To post a comment you must log in.
https:/ /review. openstack. org/#/c/ 51670/