Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2158466

Summary: bind pool generation is broken in bring your own bind case when there are no framework deployed binds
Product: Red Hat OpenStack Reporter: Brent Eagles <beagles>
Component: tripleo-ansibleAssignee: Brent Eagles <beagles>
Status: CLOSED DUPLICATE QA Contact: Joe H. Rahme <jhakimra>
Severity: high Docs Contact:
Priority: high    
Version: 17.0 (Wallaby)CC: gregraka, mburns
Target Milestone: z2Keywords: Triaged
Target Release: 17.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Known Issue
Doc Text:
When deploying with externally managed bind servers (i.e. when DesignateExternalBindServers is configured), the "nameservers" field in the bind pool will not be configured properly. A workaround is to apply: https://review.opendev.org/c/openstack/tripleo-heat-templates/+/883471 https://review.opendev.org/c/openstack/tripleo-ansible/+/883470 and redeploying - optionally setting the DesignateBindNSRecords parameter to reflect the zones managed by designate.
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-31 12:59:52 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 Brent Eagles 2023-01-05 14:40:22 UTC
The bind pool jinja template contains a loop that depends on "designate_bind" group existing.

 targets:
    {% for server in groups.designate_bind -%}
    - type: bind9
      description: BIND9 Server {{ loop.index }}

This might not be available in the bring you own bind case and this and other similar blocks should be nested in and if/then block conditional on the existence of the group.