Therefore most of the service networks default to ctlplane as the default logic does not work[1]. You either add 'name_lower' key to network_data.yaml or override ServiceNetMap parameter for networks to use 'internalapi'[2] (not default 'internal_api'). The specific pacemaker issue is you're facing due to HostnameResolveNetwork falling back to ctlplane.
The issue is your network_data.yaml does not have 'name_lower' key for networks.
- name: InternalApi api_subnet01: n_pools:
dns_domain: internalapi.arda.
vip: true
subnets:
internal_
ip_subnet: 192.168.2.0/24
allocatio
- start: 192.168.2.10
end: 192.168.2.250
vlan: 20
Therefore most of the service networks default to ctlplane as the default logic does not work[1]. You either add 'name_lower' key to network_data.yaml or override ServiceNetMap parameter for networks to use 'internalapi'[2] (not default 'internal_api'). The specific pacemaker issue is you're facing due to HostnameResolve Network falling back to ctlplane.
[1] https:/ /github. com/openstack/ tripleo- heat-templates/ blob/master/ overcloud- resource- registry- puppet. j2.yaml# L365
[2] servicenet_ map_env. yaml ntNetwork: internalapi
parameter_defaults:
ServiceNetMap:
ApacheNetwork: internalapi
NeutronTena