Comment 12 for bug 2051604

You only have to update the [neutron] section, don't change the other sections.

the messages

WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to
instance. Retrying.: requests.exceptions.ConnectionError:
HTTPSConnectionPool(host='172.16.5.129', port=9443): Max retries exceeded
with url: // (Caused by
NewConnectionError('<urllib3.connection.HTTPSConnection object at
0x7f1b9057fa60>: Failed to establish a new connection: [Errno 111]
Connection refused'))

are normal, Octavia tries to reach the VM that it created, but it takes a few second to boot it and start the agent in the VM, during that time, those WARNINGs are displayed. If the same message is displayed with an ERROR-level, it's a real issue, the VM is not reachable.

your screenshot shows that the load balancer was successfully created/updated, its provisioning_status is ACTIVE, from the point of view of the Octavia controller, the load balancer is ready.
the ERROR operating_status means that you have health-monitor in one of your pool and the health-monitor failed when it ensures that the backend members are up.

in most of the cases, it means that there's a problem outside of octavia:
- the members are down
- the members are not correctly configured (subnet not reachable from the LB)
- the HM is not correctly configured (for instance, an HTTP HM checks for GET / with a 200 status, but receives a 302 status)

you can get the status of all the resources of a LB with the following command:

openstack loadbalancer status show <lb>

in your case it will probably show that the operating_status of the members is ERROR