Public bug reported:
If we have an external network, with default rbac policy, and even 1 tenant is
using this network, we can not delete the default rbac policy in order to
decide to which tenants this network will be exposed.
In this situation the network will be exposed to all tenants unless the admin
first disconnects the using tenant and then makes the needed changes.
In a situation with many tenants this will be non user friendly.
MITAKA.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1581929
Title:
RBAC -access_as_external lack of flexibility
Status in neutron:
New
Bug description:
If we have an external network, with default rbac policy, and even 1 tenant
is using this network, we can not delete the default rbac policy in order to
decide to which tenants this network will be exposed.
In this situation the network will be exposed to all tenants unless the admin
first disconnects the using tenant and then makes the needed changes.
In a situation with many tenants this will be non user friendly.
MITAKA.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1581929/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
