Bug 1280258 - tenants seem like they are able to detach admin enforced QoS policies from ports or networks
tenants seem like they are able to detach admin enforced QoS policies from po...
Status: CLOSED EOL
Product: RDO
Classification: Community
Component: openstack-neutron (Show other bugs)
Liberty
Unspecified Unspecified
unspecified Severity medium
: ---
: Kilo
Assigned To: lpeer
Ofer Blaut
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-11 05:50 EST by Itzik Brown
Modified: 2016-05-19 11:34 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-05-19 11:34:49 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Launchpad 1486607 None None None Never

  None (edit)
Description Itzik Brown 2015-11-11 05:50:52 EST
Description of problem:
As a tenant it's possible to update the policy of a network or a port without changing the policy.json

# neutron port-update <port-id> --no-qos-policy

Version-Release number of selected component (if applicable):
openstack-neutron-7.0.1-dev28.el7.centos.noarch
openstack-neutron-common-7.0.1-dev28.el7.centos.noarch
python-neutron-7.0.1-dev28.el7.centos.noarch
openstack-neutron-ml2-7.0.1-dev28.el7.centos.noarch
openstack-neutron-openvswitch-7.0.1-dev28.el7.centos.noarch
python-neutronclient-3.1.1-dev7.el7.centos.noarch


How reproducible:
100%

Steps to Reproduce:
1.neutron qos-policy-create --tenant-id <tenant id> policy1
2.neutron qos-bandwidth-limit-rule-create  --max-kbps 2048 --max-burst-kbps 204 policy1
3.neutron net-update net1 --qos_policy_id <policy1 id>
4.neutron net-update <net-id> --no-qos-policy

Actual results:
A tenant doesn't get an error when updating a network's or a port's policy

Expected results:
A tenant should get an error when updating a network's or a port's policy

Additional info:
Comment 1 Chandan Kumar 2016-05-19 11:34:49 EDT
This bug is against a Version which has reached End of Life.
If it's still present in supported release (http://releases.openstack.org), please update Version and reopen.

Note You need to log in before you can comment on or make changes to this bug.