some openstack services are not accessed from publicAPI network so no need to configure haproxy IP from publicAPI range.

Solution Verified - Updated -

Issue

  • HAProxy configuration for PublicAPI is not correct
  • In OpenStack, some services are not accessed from publicAPI network so no need to configure haproxy IP from publicAPI range.
    For ex.:
# grep -A8 registry /etc/haproxy/haproxy.cfg
listen glance-registry
  bind 192.168.100.10:9191  <======= IP from publicAPI network.
  bind 192.168.200.10:9191
  bind 192.168.200.30:9191
  mode  tcp
  option  tcplog
  server lb-backend-mucu100013 192.168.200.32:9191  check inter 1s
  server lb-backend-mucu100012 192.168.200.33:9191  check inter 1s
  server lb-backend-mucu100011 192.168.200.34:9191  check inter 1s

Environment

  • Red Hat OpenStack

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