← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1394035] [NEW] Regular users cannot disassociate or delete Floating IP address

 

Public bug reported:

In the Access & Security view, regular users (Member, not admin role) do
not see the buttons to disassociate or delete Floating IP addresses.

This can be temporarily fixed by changing policy.json files for neutron that are fed to Horizon:
<     "update_floatingip": "rule:admin_or_owner",
<     "delete_floatingip": "rule:admin_or_owner",
---
>     "update_floatingip": "rule:admin_or_owner or rule:regular_user",
>     "delete_floatingip": "rule:admin_or_owner or rule:regular_user",

Adding "rule:regular_user" forces Horizon to display those buttons. This
is a bad workaround and I believe the real problem lies somewhere in the
way Horizon is determining admin_or_owner rule's value.

** Affects: horizon
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1394035

Title:
  Regular users cannot disassociate or delete Floating IP address

Status in OpenStack Dashboard (Horizon):
  New

Bug description:
  In the Access & Security view, regular users (Member, not admin role)
  do not see the buttons to disassociate or delete Floating IP
  addresses.

  This can be temporarily fixed by changing policy.json files for neutron that are fed to Horizon:
  <     "update_floatingip": "rule:admin_or_owner",
  <     "delete_floatingip": "rule:admin_or_owner",
  ---
  >     "update_floatingip": "rule:admin_or_owner or rule:regular_user",
  >     "delete_floatingip": "rule:admin_or_owner or rule:regular_user",

  Adding "rule:regular_user" forces Horizon to display those buttons.
  This is a bad workaround and I believe the real problem lies somewhere
  in the way Horizon is determining admin_or_owner rule's value.

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


Follow ups

References