RDO tickets are now tracked in Jira https://issues.redhat.com/projects/RDO/issues/
Bug 1280258 - tenants seem like they are able to detach admin enforced QoS policies from ports or networks
Summary: tenants seem like they are able to detach admin enforced QoS policies from po...
Keywords:
Status: CLOSED EOL
Alias: None
Product: RDO
Classification: Community
Component: openstack-neutron
Version: Liberty
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: Kilo
Assignee: lpeer
QA Contact: Ofer Blaut
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-11 10:50 UTC by Itzik Brown
Modified: 2016-05-19 15:34 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-19 15:34:49 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1486607 0 None None None Never

Description Itzik Brown 2015-11-11 10:50:52 UTC
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 15:34:49 UTC
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.