Designate DNS – the default SOA and NS recordsets are counted for quota

Bug #1992445 reported by Arkady Shtempler
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Designate
New
Medium
Unassigned

Bug Description

The default created SOA and NS recordsets for a Zone are counted in quota, but shouldn't.
We should only count stuffs that is created by user.

Test scenario:
1) Set quotas for a user with:
quotas = {
    'zones': 7, 'zone_recordsets': 1, 'zone_records': 7,
    'recordset_records': 7, 'api_export_size': 7}

2) Try to create a Zone

Expected Result:
Zone is sucsesfully created

Actual result:
Zone creation fails on:
Details: {'code': 413, 'type': 'over_quota', 'message': 'Quota exceeded for zone_recordsets.', 'request_id': 'req-0a7f59a6-7c06-42dc-b6fd-6ae4d78e2cc6'}

Tags: designate
affects: nova → designate
Revision history for this message
Arkady Shtempler (ashtempl) wrote :

Patch to reproduce: https://review.opendev.org/c/openstack/designate-tempest-plugin/+/860935
Relevant test is: test_zone_recordsets_boundary

Revision history for this message
Michael Johnson (johnsom) wrote :

The other interesting point to this bug is zone_recordsets counts SOA and NS, but zone_records does not. So it's an inconsistency in the quota behavior.

Changed in designate:
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.