Bug 2000618 - Neutron - “Update bandwidth limit rule” API on SUCCESS responds with 200 instead of Expected 202
Summary: Neutron - “Update bandwidth limit rule” API on SUCCESS responds with 200 inst...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tempest
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Rodolfo Alonso
QA Contact: Fiorella Yanac
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-02 14:02 UTC by Arkady Shtempler
Modified: 2022-09-21 12:17 UTC (History)
10 users (show)

Fixed In Version: openstack-tempest-28.1.0-0.20210913221832.ad2c300.el8ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-09-21 12:17:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1942448 0 None None None 2021-09-02 14:02:07 UTC
OpenStack gerrit 807390 0 None MERGED Fix some api-ref typos 2022-07-08 15:36:10 UTC
OpenStack gerrit 807480 0 None MERGED Expected success status for "QoS rule update APIs" is "200 OK" 2022-07-08 15:36:10 UTC
Red Hat Issue Tracker OSP-8134 0 None None None 2021-11-15 12:52:17 UTC
Red Hat Product Errata RHEA-2022:6543 0 None None None 2022-09-21 12:17:40 UTC

Description Arkady Shtempler 2021-09-02 14:02:07 UTC
### Scenario ###
Activate “Update bandwidth limit rule” API with proper values to make it PASS

### Actual Result ###
Received status code is 200 OK

### Expected Result ###
According the Documentation it needs to be 202 Accepted
https://docs.openstack.org/api-ref/network/v2/index.html?expanded=update-bandwidth-limit-rule-detail#update-bandwidth-limit-rule

### Tempest prompt output ###
BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202BUG_200_instead_of_202
2021-09-01 15:21:48.668 529226 INFO tempest.lib.common.rest_client [req-27de559b-db51-433b-b01b-fd27cba24664 ] Request (QoSTest:test_qos_basic_and_update): 200 PUT http://10.0.0.125:9696/v2.0/qos/policies/31e15f98-8b03-4f8b-9a1a-27847ea48971/bandwidth_limit_rules/f17625ab-24c7-46c1-bcd2-0e326c9ac360 0.269s
2021-09-01 15:21:48.668 529226 DEBUG tempest.lib.common.rest_client [req-27de559b-db51-433b-b01b-fd27cba24664 ] Request - Headers: {'Content-Type': 'application/json', 'Accept': 'application/json', 'X-Auth-Token': '<omitted>'}
        Body: {"bandwidth_limit_rule": {"max_kbps": 2000, "max_burst_kbps": 2000}}
    Response - Headers: {'content-type': 'application/json', 'content-length': '137', 'x-openstack-request-id': 'req-27de559b-db51-433b-b01b-fd27cba24664', 'date': 'Wed, 01 Sep 2021 19:21:48 GMT', 'connection': 'close', 'status': '200', 'content-location': 'http://10.0.0.125:9696/v2.0/qos/policies/31e15f98-8b03-4f8b-9a1a-27847ea48971/bandwidth_limit_rules/f17625ab-24c7-46c1-bcd2-0e326c9ac360'}
        Body: b'{"bandwidth_limit_rule": {"max_kbps": 2000, "max_burst_kbps": 2000, "direction": "egress", "id": "f17625ab-24c7-46c1-bcd2-0e326c9ac360"}}' _log_request_full /home/stack/tempest/tempest/lib/common/rest_client.py:456

Comment 1 Rodolfo Alonso 2021-09-06 14:02:46 UTC
Hello:

The neutron-lib documentation was changed in [1]

The U/S tempest patch is [2]. Because OSP17 is using U/S master, this BZ could be set to MODIFIED.

Regards.

[1]https://review.opendev.org/c/openstack/neutron-lib/+/807390
[2]https://review.opendev.org/c/openstack/tempest/+/807480

Comment 11 errata-xmlrpc 2022-09-21 12:17:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.0 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2022:6543


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