Reviewed: https://review.openstack.org/358275 Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=38b1b47fe76652fb7ee13a9028f56795b35c0dc9 Submitter: Jenkins Branch: master
commit 38b1b47fe76652fb7ee13a9028f56795b35c0dc9 Author: Sławek Kapłoński <[email protected]> Date: Sat Aug 20 21:00:51 2016 +0000 Fix internal server error during updating QoS rule QoS rule can be edited or created only by admin users. Because rule object don't have tenant_id attribute there was error in checking tenant_id of object and neutron server got internal server error. Now if updating object doesn't have tenant_id at all (like in case of QoS rules), 404 error will be returned to the user. New API tests for checking this case are added for QoS. Change-Id: Ia82ad84a3a07df4df8eaeaed6c47d31be9493cbd Closes-Bug: #1515564 ** Changed in: neutron Status: In Progress => Fix Released -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1515564 Title: Internal server error when running qos-bandwidth-limit-rule-update as a tenant Status in neutron: Fix Released Bug description: When running the following command as a tenant:: # neutron qos-bandwidth-limit-rule-update eadd705c-f295-4246-952e-bad2762e6b27 policy2 --max-kbps 2048 I get the error: Request Failed: server errointernalr while processing your request. There should be a meaningful error such as - Updating policy is not allowed Version ====== CentOS 7.1 python-neutronclient-3.1.1-dev7.el7.centos.noarch To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1515564/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
