yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #16734
[Bug 1335733] [NEW] Failed to boot instance with admin role
Public bug reported:
Sometimes we need to create instances with admin role for some other
tenants. But if we're booting the instance with a security group which
name is duplicated in Neutron. Then user will run into an error and from
the GUI, user don't know what happened.
The root cause of this issue is Neutron client doesn't honoured the
tenant id, but get all the security group ids with the given name. So we
need to fix this from both Nova and Neutron client side.
** Affects: nova
Importance: Undecided
Assignee: Fei Long Wang (flwang)
Status: New
** Affects: python-neutronclient
Importance: Undecided
Assignee: Fei Long Wang (flwang)
Status: New
** Changed in: nova
Assignee: (unassigned) => Fei Long Wang (flwang)
** Also affects: python-neutronclient
Importance: Undecided
Status: New
** Changed in: python-neutronclient
Assignee: (unassigned) => Fei Long Wang (flwang)
** Description changed:
Sometimes we need to create instances with admin role for some other
tenants. But if we're booting the instance with a security group which
- is duplicated in Neutron. Then user will run into an error and from the
- GUI, user don't know what happened.
+ name is duplicated in Neutron. Then user will run into an error and from
+ the GUI, user don't know what happened.
The root cause of this issue is Neutron client doesn't honoured the
tenant id, but get all the security group ids with the given name. So we
need to fix this from both Nova and Neutron client side.
--
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/1335733
Title:
Failed to boot instance with admin role
Status in OpenStack Compute (Nova):
New
Status in Python client library for Neutron:
New
Bug description:
Sometimes we need to create instances with admin role for some other
tenants. But if we're booting the instance with a security group which
name is duplicated in Neutron. Then user will run into an error and
from the GUI, user don't know what happened.
The root cause of this issue is Neutron client doesn't honoured the
tenant id, but get all the security group ids with the given name. So
we need to fix this from both Nova and Neutron client side.
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1335733/+subscriptions
Follow ups
References