Description of problem: KeystoneAdminApiNetwork: internal_api is defined in the templates and the service is configured in the provisioning network during the deployment Version-Release number of selected component (if applicable): Latest How reproducible: Always Steps to Reproduce: 1. Change KeystoneAdminApiNetwork to internal_api in ServiceNetMap 2. Deploy Actual results: In haproxy.cfg, the AdminAPINetwork is binded on the ctlplane instead of the internal_api Expected results: Should reflect the templates Additional info:
David, what release was this in? I tried reproducing it in upstream tripleo, and for the master branch it seems there was no problem when trying to do that in a network-isolated, ha deployment. (for the record, this is how I tried it out https://review.openstack.org/#/c/424718/ ). In resulting deployment I see keystone_admin_api_vip and keystone_admin_api_network with the correct values, thus resulting in a correct haproxy.cfg. How did you change the network? I added this to the paramete_defaults section of an environment file: ServiceNetMap: KeystoneAdminApiNetwork: internal_api
openstack-tripleo-heat-templates-5.2.0-3.el7ost.noarch openstack-tripleo-0.0.8-0.2.4de13b3git.el7ost.noarch openstack-tripleo-common-5.4.1-1.el7ost.noarch puppet-tripleo-5.5.0-2.el7ost.noarch