Bug 1977692 - Designate DNS – SCOPE is needed to be set according to used resource ID (could be Zone or Pool)
Summary: Designate DNS – SCOPE is needed to be set according to used resource ID (coul...
Keywords:
Status: NEW
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: Michael Johnson
QA Contact: Toni Freger
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-06-30 09:51 UTC by Arkady Shtempler
Modified: 2023-08-01 14:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1934120 0 None None None 2021-06-30 09:51:44 UTC
Red Hat Issue Tracker OSP-5654 0 None None None 2021-11-23 16:08:46 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.