When deploying an overcloud with an external load balancer the IPs specified in external-lb.yaml do not get assigned correctly

Solution Verified - Updated -

Issue

  • When deploying an overcloud with an external load balancer the IPs specified in external-lb.yaml do not get assigned correctly.
  • Some controller nodes get the IP specified in external-lb.yaml, but other controller nodes get IPs in the range that were not specified.
  • The command used to deploy the overcloud was:
openstack overcloud deploy --templates ~/templates/my-overcloud  -e /usr/share/openstack-tripleo-heat-templates/environments/external-loadbalancer-vip.yaml  -e ~/templates/external-lb.yaml  -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml  -e /home/stack/templates/network-environment.yaml --control-flavor control --compute-flavor compute  --ntp-server time.example.com --neutron-network-type vxlan --neutron-tunnel-types vxlan --control-scale 3 --compute-scale 1

Environment

  • Red Hat Enterprise Linux OpenStack Platform 7.x
  • OSP-Director 7.x

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content