Bug 2052951 - “api_export_size”, immediate “413 over_quota” instead of “202”
Summary: “api_export_size”, immediate “413 over_quota” instead of “202”
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-designate
Version: 17.0 (Wallaby)
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Nate Johnston
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-10 10:37 UTC by Arkady Shtempler
Modified: 2023-08-03 17:24 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-01 14:52:51 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1960495 0 None None None 2022-02-10 10:37:04 UTC
Red Hat Issue Tracker OSP-12598 0 None None None 2022-02-10 10:41:56 UTC

Description Arkady Shtempler 2022-02-10 10:37:04 UTC
### Scenario ###
As admin set the “api_export_size” to X
Create a Zone and start adding recordsets to exceed X

### Actual Result ###
When the X+1  quota is actually reached, export  API (asynchronous) responds with 202.

### Expected Result ###
Immediate “413 over_quota” response.

Notes:
1) For reproducing: https://review.opendev.org/c/openstack/designate-tempest-plugin/+/827934
test name: test_api_export_size_quota
2) From Michael:
The issue here is that the zone export API is an asynchronous API. The test will get back a 202 status that Designate has accepted the request. If you do a followup call to "zone export show" you will see that the export went into ERROR.


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