Hi, Controllers nodes must be able to connect with amphora to make healthchecks. Since the logs are shown "no route to host error", have you tried to configure a route to octavia management network gateway? Regards. On Mon, Apr 7, 2025, 11:54 Thamanna Farhath <thamanna.f@zybisys.com> wrote:

Hi OpenStack Community,

I am currently facing an issue with the Load Balancer (Octavia) service in my OpenStack deployment and would appreciate your guidance or suggestions on how to troubleshoot and resolve it. ------------------------------ *Environment Details:*

-

*OpenStack Version:* 2023.1 (Antelope) -

*Operating System:* Ubuntu 22.04 -

*Octavia Backend:* Amphora -

*Network Type:* VXLAN -

*Deployment Tool:* Kolla Ansible

------------------------------ *Issue Summary:*

After creating a Load Balancer, the Amphora instance is successfully launched. However, approximately *18 minutes later*, the Load Balancer transitions to an *ERROR* state.

*Error Observed:*

octavia.common.exceptions.ComputeWaitTimeoutException: Waiting for compute id a222527f-8336-4fb1-8e9e-0e3ac6e8d580 to go active timeout. octavia.amphorae.driver_exceptions.exceptions.AmpConnectionRetry: Could not connect to amphora, exception caught: HTTPSConnectionPool(host='192.168.200.247', port=9443): Max retries exceeded with url: // (Caused by NewConnectionError: Failed to establish a new connection: [Errno 113] No route to host)

------------------------------ *What I’ve Tried:*

1.

Created a VXLAN-based internal network:

openstack subnet create --network octavia-mgmt-net --subnet-range 192.168.200.0/24 octavia-mgmt-subnet openstack router create octavia-router openstack router add subnet octavia-router octavia-mgmt-subnet openstack router set octavia-router --external-gateway <public-network-id>

2.

Manually configured OVS interface:

ovs-vsctl add-port br-int octavia-mgmt -- set interface octavia-mgmt type=internal ip addr add 192.168.200.1/24 dev octavia-mgmt ip link set octavia-mgmt up

3.

Security groups are open (allowing all ingress and egress). 4.

Verified OVS bridge setup – interface appears correctly on br-int.

------------------------------ *Behavior Noticed:*

-

Amphora instance gets created but fails to communicate with the controller after a while,so health checks fails. -

The controller cannot reach the Amphora management IP (192.168.200.x). -

Logs show heartbeat/connection issues (No route to host, timeouts).

------------------------------ *Request for Help:*

I would appreciate any of the following:

-

Suggestions to verify if the management network is properly routed from controller to Amphora. -

Best practices for setting up the Octavia management network using VXLAN. -

Troubleshooting steps for verifying health manager connectivity to Amphora.

------------------------------ *Disclaimer :** The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.*

*E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."*

Thamanna Farhath wrote:

Hi OpenStack Community,

I am currently facing an issue with the Load Balancer (Octavia) service in my OpenStack deployment and would appreciate your guidance or suggestions on how to troubleshoot and resolve it.

Environment Details:

OpenStack Version: 2023.1 (Antelope)

Operating System: Ubuntu 22.04

Octavia Backend: Amphora

Network Type: VXLAN

Deployment Tool: Kolla Ansible 

Issue Summary:

After creating a Load Balancer, the Amphora instance is successfully launched. However, approximately 18 minutes later, the Load Balancer transitions to an ERROR state.

Error Observed:

octavia.common.exceptions.ComputeWaitTimeoutException: Waiting for compute id a222527f-8336-4fb1-8e9e-0e3ac6e8d580 to go active timeout. octavia.amphorae.driver_exceptions.exceptions.AmpConnectionRetry: Could not connect to amphora, exception caught: HTTPSConnectionPool(host='192.168.200.247', port=9443): Max retries exceeded with url: // (Caused by NewConnectionError: Failed to establish a new connection: [Errno 113] No route to host)

What I’ve Tried:

Created a VXLAN-based internal network:

openstack subnet create --network octavia-mgmt-net --subnet-range 192.168.200.0/24 octavia-mgmt-subnet openstack router create octavia-router openstack router add subnet octavia-router octavia-mgmt-subnet openstack router set octavia-router --external-gateway <public-network-id>

Manually configured OVS interface:

ovs-vsctl add-port br-int octavia-mgmt -- set interface octavia-mgmt type=internal ip addr add 192.168.200.1/24 dev octavia-mgmt ip link set octavia-mgmt up

Security groups are open (allowing all ingress and egress).

Verified OVS bridge setup – interface appears correctly on br-int.

Behavior Noticed:

Amphora instance gets created but fails to communicate with the controller after a while,so health checks fails.

The controller cannot reach the Amphora management IP (192.168.200.x).

Logs show heartbeat/connection issues (No route to host, timeouts).

Request for Help:

I would appreciate any of the following:

Suggestions to verify if the management network is properly routed from controller to Amphora.

Best practices for setting up the Octavia management network using VXLAN.

Troubleshooting steps for verifying health manager connectivity to Amphora. Disclaimer : The content of this email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to which they are addressed. If you have received this email in error, please notify the sender and remove the messages from your system. If you are not the named addressee, it is strictly forbidden for you to share, circulate, distribute or copy any part of this e-mail to any third party without the written consent of the sender.

E-mail transmission cannot be guaranteed to be secured or error free as information could be intercepted, corrupted, lost, destroyed, arrive late, incomplete, or may contain viruses. Therefore, we do not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. The recipient should check this e-mail and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email."

Since you're creating a tenant network to be used by Octavia, the relevant configuration isn't present on the host (o-hm0 interface for interacting with the VMs) and hence the VMs are unreachable. Please use the configuration `octavia_network_type: "tenant"` in globals.yml More information can be found in the commit id aad7a731aadc3ebf0e37938a9a78d09545caa49f (for kolla-ansible).