yahoo-eng-team team mailing list archive

[Louis Bouchard <louis.bouchard@xxxxxxxxxxxxx>]

** Also affects: horizon (Ubuntu Yakkety)
   Importance: Undecided
       Status: New

** Also affects: horizon (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Also affects: horizon (Ubuntu Trusty)
   Importance: Undecided
       Status: New

** Changed in: horizon (Ubuntu Yakkety)
       Status: New => Fix Released

** Changed in: horizon (Ubuntu Trusty)
       Status: New => Triaged

** Changed in: horizon (Ubuntu Xenial)
       Status: New => Triaged

-- 
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/1666827

Title:
  Backport fixes for Rename Network return 403 Error

Status in Ubuntu Cloud Archive:
  New
Status in OpenStack Dashboard (Horizon):
  New
Status in horizon package in Ubuntu:
  New
Status in horizon source package in Trusty:
  Triaged
Status in horizon source package in Xenial:
  Triaged
Status in horizon source package in Yakkety:
  Fix Released

Bug description:
  [Impact]
  Non-admin users are not allowed to change the name of a network using the OpenStack Dashboard GUI

  [Test Case]
  1. Deploy trusty-mitaka or xenial-mitaka OpenStack Cloud
  2. Create demo project
  3. Create demo user
  4. Log into OpenStack Dashboard using demo user
  5. Go to Project -> Network and create a network
  6. Go to Project -> Network and Edit the just created network
  7. Change the name and click Save
  8. Observe that your request is denied with an error message

  [Regression Potential]
  Minimal.

  We are adding a patch already merged into upstream stable/mitaka for
  the horizon call to policy_check before sending request to Neutron
  when updating networks.

  The addition of rule "update_network:shared" to horizon's copy of
  Neutron policy.json is our own due to upstream not willing to back-
  port this required change. This rule is not referenced anywhere else
  in the code base so it will not affect other policy_check calls.

  Upstream bug: https://bugs.launchpad.net/horizon/+bug/1609467

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1666827/+subscriptions