Bug 2052951

Summary: “api_export_size”, immediate “413 over_quota” instead of “202”
Product: Red Hat OpenStack Reporter: Arkady Shtempler <ashtempl>
Component: openstack-designateAssignee: Nate Johnston <njohnston>
Status: CLOSED UPSTREAM QA Contact: Toni Freger <tfreger>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: gthiemon, michjohn, njohnston, scohen
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-01 14:52:51 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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.