Yipei,
Yeah, we have clearly identified the problem. Those two default route
lines should not be different. See my devstack:
sudo: unable to resolve host amphora-20a717b4-eb97-4b5c-a11a-0633fe61f135
default via 10.0.0.1 dev eth1 table 1 onlink
default via 10.0.0.1 dev eth1 onlink
So the issue
Hi, Michael,
Please ignore my last two mails. Sorry about that.
The results of the two commands are as follows.
ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy ip route show table all
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b
Hi, Michael,
Sorry about the typo in the last mail. Please just ignore the last mail.
In the environment where octavia and tricircle are installed together, I
created a router and attached subnet1 to it. Then I bind the mac address of
10.0.1.10 (real gateway) to ip of 10.0.1.1 in the amphora arp
Hi, Michael,
Thanks a lot for your comments.
In the environment where octavia and tricircle are installed together, I
created a router and attached subnet1 to it. Then I bind the mac address of
10.0.1.9 (real gateway) to ip of 10.0.1.1 in the amphora arp cache,
manually making amphora knows the m
Yipei,
I am struggling to follow some of the details as I see different information:
+---+-+
| Field | Value |
+---+-+
| alloca
Hi, Michael,
I tried to run to command, and I think the amphora can connect to the
member (10.0.1.3). The results are as follows.
ubuntu@amphora-a0621f0e-d27f-4f22-a4ee-05b695e2b71f:~$ sudo ip netns exec
amphora-haproxy ping 10.0.1.3
sudo: unable to resolve host amphora-a0621f0e-d27f-4f22-a4ee-05
The actual gateway address does not matter to Octavia/amphora. It
gets that value from DHCP or from neutron if a static address was
assigned from neutron.
My concern is that the subnet gateway 10.0.1.10 does not match the
gateway address DHCP gave us 10.0.1.1.
Technically, since the two addresses
Hi, Michael,
Thanks a lot for your reply.
I can make sure that there is no router or multiple dhcp services in my
environment.
As shown in my first mail, the haproxy in the amphora tries to find the
gateway ip 10.0.1.1 that does not exist in the environment.
ubuntu@amphora-a0621f0e-d27f-4f22-a4
Hi Yipei,
I see a few things that are odd:
stack@devstack-1:/opt/stack/octavia$ sudo ip netns exec
qdhcp-310fea4b-36ae-4617-b499-5936e8eda842 curl 10.0.1.4
curl: (7) Failed to connect to 10.0.1.4 port 80: Connection timed out
This means that the connection is not working between curl and the
HAPr
Hi, Michael,
Based on your mail, the information is as follows.
1. The version of Octavia I used is Queens, and the latest commit message is
commit 2ab2836d0ebdd0fd5bc32d3adcc44a92557c8c1d
Author: OpenStack Proposal Bot
Date: Fri Nov 3 17:58:59 2017 +
Updated from global requirements
Hi Yipei,
I need some more information to help you out. Can you provide the following?
1. What version of Octavia you are using.
2. "openstack server list" output for the amphora.
3. "openstack loadbalancer show" for the load balancer.
4. "openstack loadbalancer listener show" for the listener.
11 matches
Mail list logo