Uploaded image for project: 'Red Hat OpenStack Services on OpenShift'
  1. Red Hat OpenStack Services on OpenShift
  2. OSPRH-386

BZ#1977692 Designate DNS – SCOPE is needed to be set according to used resource ID (could be Zone or Pool)

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • openstack-designate
    • 5
    • False
    • False
    • Not Set
    • None
    • Undefined
    • Moderate
    • Networking; VANS

      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.

            michjohn@redhat.com Michael Johnson
            jira-bugzilla-migration RH Bugzilla Integration
            rhos-dfg-networking-squad-vans
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: