Bug 2052959

Summary: Designate DNS – “recordset_records” no “413 over_quota” response on quota exceed
Product: Red Hat OpenStack Reporter: Arkady Shtempler <ashtempl>
Component: openstack-designateAssignee: Michael Johnson <michjohn>
Status: CLOSED ERRATA QA Contact: Lilach Avraham <lavraham>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: jschluet, lavraham, michjohn, scohen
Target Milestone: rcKeywords: Triaged
Target Release: 17.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-designate-12.0.2-0.20220529170342.2e55c3e.el9ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-09-21 12:18:59 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:52:46 UTC 
### Scenario ###
As admin set the “recordset_records” to X
Create a Zone and try to add a recordset (with number of records is over X) to that zone.

### Actual Result ###
Recordset is successfully created

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

Notes:
1) For reproducing: https://review.opendev.org/c/openstack/designate-tempest-plugin/+/827934
test name: test_recordset_records_quota
2) From Michael:
This is a bug in the quota code. I can see that they are checking the quota for the existing records instead of the total including the new records.
Comment 10 errata-xmlrpc 2022-09-21 12:18:59 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