You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix BGP registry IP route collection for multi-datacenter deployments
The original implementation attempted to run getent directly in the task
with delegate_to using an undefined loop variable, causing task failures.
This fix properly delegates getent execution to each overcloud VM and
accumulates the resolved IPs across all VMs. This is necessary because
VMs in different racks/datacenters may use different DNS servers, resulting
in different IP resolutions for the same registry domains.
Changes:
- Extract getent logic into separate task file (getent_registry_ips_bgp.yml)
- Run getent from each VM via include_tasks with proper delegation
- Accumulate IPs using set_fact to preserve results across all VMs
- Simplify IP list generation in both prepare_overcloud.yml and
prepare_undercloud.yml to use the accumulated list
The accumulated IP list ensures routes are added for all possible registry
IPs as resolved from each datacenter's DNS server.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <[email protected]>
0 commit comments