Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

Could not connect to instance. Retrying.: ... [Errno 113] No route to host. provisioning_status stays on PENDING_CREATE

hi all

I have configured an octavia service by help of michael, but after creating loadbalancer the provisioning_status stays on PENDING_CREATE. the log of worker shows Could not connect to instance. Retrying.: ... [Errno 113] No route to hos

I have deployed openstack on virtualbox ( one vm for controller and one vm for compute) my network setting are :

2 vboxnet :

vboxnet1 : 192.168.58.0/24 for provider network

vboxnet2 : 10.0.0.0/24 for management network

NAT

and I have used linuxbridging.

in openstack I have created two network ( provider and selfservice)

provider : 192.168.58.0/24

selfservice : 192.168.100.0/24

after creating loadbalancer ( openstack loadbalancer create .... --vip-subnet-id selfservice) , it create the loadbalancer and wants to connect to the amphora instance with ip in range of 192.168.100.0/24 that naturally does not have route to it , so provisioning_status stays on PENDING_CREATE ...

are my network configuration a wrong ! should I use ovs instead of linuxbridging ! ...

Could not connect to instance. Retrying.: ... [Errno 113] No route to host. provisioning_status stays on PENDING_CREATE

hi all

I have configured an octavia service by help of michael, Michael, but after creating loadbalancer the provisioning_status stays on PENDING_CREATE. the log of worker shows Could not connect to instance. Retrying.: ... [Errno 113] No route to hos

I have deployed openstack on virtualbox ( one vm for controller and one vm for compute) my network setting are :

2 vboxnet :

vboxnet1 : 192.168.58.0/24 for provider network

vboxnet2 : 10.0.0.0/24 for management network

NAT

and I have used linuxbridging.

in openstack I have created two network ( provider and selfservice)

provider : 192.168.58.0/24

selfservice : 192.168.100.0/24

after creating loadbalancer ( openstack loadbalancer create .... --vip-subnet-id selfservice) , it create the loadbalancer and wants to connect to the amphora instance with ip in range of 192.168.100.0/24 that naturally does not have route to it , so provisioning_status stays on PENDING_CREATE ...

are my network configuration a wrong ! should I use ovs instead of linuxbridging ! ...

Could not connect to instance. Retrying.: ... [Errno 113] No route to host. provisioning_status stays on PENDING_CREATE

hi all

I have configured an octavia service by help of Michael, but after creating loadbalancer the provisioning_status stays on PENDING_CREATE. the log of worker shows Could not connect to instance. Retrying.: ... [Errno 113] No route to hos

I have deployed openstack on virtualbox ( one vm for controller and one vm for compute) my network setting are :

2 vboxnet :

vboxnet1 : 192.168.58.0/24 for provider network

vboxnet2 : 10.0.0.0/24 for management network

NAT

and I have used linuxbridging.

in openstack I have created two network ( provider and selfservice)

provider : 192.168.58.0/24

selfservice : 192.168.100.0/24

after creating loadbalancer ( openstack loadbalancer create .... --vip-subnet-id selfservice) , it create the loadbalancer and wants to connect to the amphora instance with ip in range of 192.168.100.0/24 that naturally does not have route to it , so provisioning_status stays on PENDING_CREATE ...

are my network configuration a wrong ! !

should I use ovs instead of linuxbridging ! ...

Could not connect to instance. Retrying.: ... [Errno 113] No route to host. provisioning_status stays on PENDING_CREATE

hi all

I have configured an octavia service by help of Michael, Michael, but after creating loadbalancer the provisioning_status stays on PENDING_CREATE. the log of worker shows Could not connect to instance. Retrying.: ... [Errno 113] No route to hos

I have deployed openstack on virtualbox ( one vm for controller and one vm for compute) my network setting are :

2 vboxnet :

vboxnet1 : 192.168.58.0/24 for provider network

vboxnet2 : 10.0.0.0/24 for management network

NAT

and I have used linuxbridging.

in openstack I have created two network ( provider and selfservice)

provider : 192.168.58.0/24

selfservice : 192.168.100.0/24

after creating loadbalancer ( openstack loadbalancer create .... --vip-subnet-id selfservice) , it create the loadbalancer and wants to connect to the amphora instance with ip in range of 192.168.100.0/24 that naturally does not have route to it , so provisioning_status stays on PENDING_CREATE ...

are my network configuration wrong !

should I use ovs instead of linuxbridging ! ...

Could not connect to instance. Retrying.: ... [Errno 113] No route to host. provisioning_status stays on PENDING_CREATE

hi all

I have configured an octavia service by help of Michael, but after creating loadbalancer the provisioning_status stays on PENDING_CREATE. the log of worker shows Could not connect to instance. Retrying.: ... [Errno 113] No route to hos

I have deployed openstack on virtualbox ( one vm for controller and one vm for compute) my network setting are :

2 vboxnet :

vboxnet1 : 192.168.58.0/24 for provider network

vboxnet2 : 10.0.0.0/24 for management network

NAT

and I have used linuxbridging.

in openstack I have created two network ( provider and selfservice)

provider : 192.168.58.0/24

selfservice : 192.168.100.0/24

after creating loadbalancer ( openstack loadbalancer create .... --vip-subnet-id selfservice) , it create the loadbalancer and wants to connect to the amphora instance with ip in range of 192.168.100.0/24 that naturally does not have route to it , so provisioning_status stays on PENDING_CREATE ...

are my network configuration wrong !

should I use ovs instead of linuxbridging ! ...