Importance: Undecided
Assignee: Chuck Carmack (chuckcarmack75)
Status: New
** Changed in: nova
Assignee: (unassigned) => Chuck Carmack (chuckcarmack75)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenSt
** Changed in: nova
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1540939
Title:
Instance delete causing port leak
Status in
on port binding extension is enabled.
** Changed in: nova
Status: Invalid => New
** Changed in: nova
Assignee: (unassigned) => Chuck Carmack (chuckcarmack75)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to O
Sean, thanks for the info in the channel. Marking the bug invalid.
** Changed in: nova
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
Public bug reported:
Nova can cause a neutron port leak after deleting an instance.
If neutron has the port binding extension installed, then nova uses admin
credentials to create the port during instance create:
https://github.com/openstack/nova/blob/master/nova/network/neutronv2/api.py#L537
Public bug reported:
On my devstack, the nova-idmapshift usage outputs this:
vagrant@vagrant-ubuntu-trusty-64:~$ nova-idmapshift
usage: User Namespace FS Owner Shift [-h] [-u UID] [-g GID] [-n NOBODY] [-i]
[-c] [-d] [-v]
6 matches
Mail list logo
