Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-10-09 Thread Yipei Niu
Hi, Adam, The following details of my older amphora image are as follows. +--+--+ | Property | Value| +--+--+ | checksum | aa279b9ae1f265a232266e

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-10-08 Thread Adam Harwell
When was the old image built and when was the new one built? I noticed my images had stopped working on our older (Liberty) production cloud, and discovered that recently Ubuntu and Centos have both upgraded cloud-init to 0.7.9 in their base images (from something like 0.7.5), which finished the de

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-10-08 Thread Yipei Niu
Hi, Michael, I once installed a successful environment, so I move the amphora image of the environment to my latest environment which doesn’t work. I create a load balancer in the latest environment using the old amphora image, and it works. So I think there is some problem with the amphora ima

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-10-08 Thread Yipei Niu
Hi, Michael, I checked neutron_lbaas.conf, the service provider is set as “LOADBALANCERV2:Octavia:neutron_lbaas.drivers.octavia.driver.OctaviaDriver:default”. Further, I installed a new environment in a new VM today, it still doesn’t work. Best regards, Yipei ___

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-28 Thread Michael Johnson
Hi Yipei, Even running through neutron-lbaas I get the same successful test. Just to double check, you are using the Octavia driver? stack@devstackpy27-2:~$ sudo ip netns exec qdhcp-4bcefe3e-038f-4a77-af4f-a560b6316a7a curl 172.21.1.16 Welcome to 172.21.1.17 connection 3 Michael On Thu, Sep 28,

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-28 Thread Yipei Niu
Hi, Michael, Thanks a lot. Look forward to your further test. I try deploying a new environment, too. Hope it can work well this time. Best regards, Yipei On Wed, Sep 27, 2017 at 10:27 AM, Yipei Niu wrote: > Hi, Michael, > > The instructions are listed as follows. > > First, create a net1. >

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-27 Thread Michael Johnson
Hi Yipei, I ran this scenario today using octavia and had success. I'm not sure what could be different. I see you are using neutron-lbaas. I will build a devstack with neutron-lbaas enabled and try that, but I can't think of what would impact this test case by going through the neutron-lbaas pa

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-26 Thread Yipei Niu
Hi, Michael, The instructions are listed as follows. First, create a net1. $ neutron net-create net1 $ neutron subnet-create net1 10.0.1.0/24 --name subnet1 Second, boot two vms in net1 $ nova boot --flavor 1 --image $image_id --nic net-id=$net1_id vm1 $ nova boot --flavor 1 --image $image_id --

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-26 Thread Yipei Niu
Hi, Michael, I think the octavia is the latest, since I pull the up-to-date repo of octavia manually to my server before installation. Anyway, I run "sudo ip netns exec amphora-haproxy ip route show table 1" in the amphora, and find that the route table exists. The info is listed as follows. def

Re: [openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-25 Thread Michael Johnson
Hi Yipei, I just tried to reproduce this and was not successful. I setup a tenant network, added a web server to it, created a loadbalancer VIP on the tenant network, added the webserver as a member on the load balancer. I can curl from the tenant network qdhcp- netns without issue. Are you run

[openstack-dev] [octavia] haproxy fails to receive datagram

2017-09-25 Thread Yipei Niu
Hi, all, I encounter some problems when using Octavia. After installing octavia with devstack, I create a load balancer named lb1 (VIP: 10.0.1.9, IP of VRRP port: 10.0.1.3) for a subnet (10.0.1.0/24), then a listener, a pool, and two members. All the resources are created successfully. The two mem