Bug 1977692

Summary: Designate DNS – SCOPE is needed to be set according to used resource ID (could be Zone or Pool)
Product: Red Hat OpenStack Reporter: Arkady Shtempler <ashtempl>
Component: openstack-designateAssignee: Michael Johnson <michjohn>
Status: NEW --- QA Contact: Toni Freger <tfreger>
Severity: medium Docs Contact:
Priority: medium    
Version: 17.0 (Wallaby)CC: beagles, michjohn, njohnston, scohen
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 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 2021-06-30 09:51:45 UTC 
There is an option to create tsigkey for: zone or pool.
https://docs.openstack.org/api-ref/dns/?expanded=#create-tsigkeys
There is a SCOPE for tsigkey which can be either ZONE or POOL

In fact it’s possible to use Zone ID with SCOPE:POOL to create to create tsigkey or Pools ID with SCOPE:ZONE.

There is no validation on SCOPE value as we would expect it to be.