[Bug 1666827] Re: Backport fixes for Rename Network return 403 Error
Ubuntu Foundations Team Bug Bot
1666827 at bugs.launchpad.net
Wed Feb 22 12:33:29 UTC 2017
The attachment "horizon-trusty-mitaka.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are member of the ~ubuntu-sponsors,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to Ubuntu Cloud Archive.
Backport fixes for Rename Network return 403 Error
Status in Ubuntu Cloud Archive:
Status in OpenStack Dashboard (Horizon):
Status in horizon package in Ubuntu:
Status in horizon source package in Trusty:
Status in horizon source package in Xenial:
Status in horizon source package in Yakkety:
Non-admin users are not allowed to change the name of a network using the OpenStack Dashboard GUI
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
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:
More information about the Ubuntu-openstack-bugs