yahoo-eng-team team mailing list archive

[Bence Romsics <2042089@xxxxxxxxxxxxxxxxxx>]

Hi,

Thanks for the report!

I'm not sure if the behavior you describe is a bug. If multiple projects
are actually using a shared network, why would you expect it to be
unshared without an error? How should such a network work when it's
shared=False but it has multiple tenants on it?

Maybe I'm missing what you mean. In that case can you please give me a
series of commands, inlcuding which one should behave differently and
how?

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/2042089

Title:
  neutron : going to shared network is working, going back not

Status in neutron:
  Invalid

Bug description:
  We have admin-generated provider-networks. Projects are allowed to
  create ports and instances on these networks. When we now set the
  "shared" property on these networks, we are no longer allowed to unset
  this property. We get the error : "Unable to reconfigure sharing
  settings for network net.vlan10.provider. Multiple tenants are using
  it.".  Once all ports and instances created by non-admin projects are
  removed we can again unset the "shared" property. So, we are allowed
  to set a parameter for which it is afterwards no longer possible to
  unset. We have now a network that is visible by all and we do not
  prefer this situation. Removing the corresponding RBAC policy is also
  not allowed.

  This is a OpenStack-Ansible installation with version Yoga.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2042089/+subscriptions