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

Yipei Niu newypei at gmail.com
Mon Oct 9 07:29:26 UTC 2017


Hi, Adam,

The following details of my older amphora image are as follows.

+------------------+--------------------------------------+
| Property         | Value                                |
+------------------+--------------------------------------+
| checksum         | aa279b9ae1f265a232266e17ea04065c     |
| container_format | bare                                 |
| created_at       | 2017-07-24T10:46:34Z                 |
| disk_format      | qcow2                                |
| id               | 5d6d5f69-a4b1-440a-b6bb-10bf945e3f85 |
| min_disk         | 0                                    |
| min_ram          | 0                                    |
| name             | amphora-x64-haproxy                  |
| owner            | c4f8c2a8fadc4b7c915f299db95c88a8     |
| protected        | False                                |
| size             | 674900480                            |
| status           | active                               |
| tags             | ["amphora"]                          |
| updated_at       | 2017-07-24T10:47:54Z                 |
| virtual_size     | None                                 |
| visibility       | public                               |
+------------------+--------------------------------------+

It is created on 2017-07-24, while my latest one is created at 2017-09-28.

I installed octavia with devstack, but it doesn't work. I discussed the
issue with Michael, he cannot reproduce the error. Please refer to the
history mails here
http://lists.openstack.org/pipermail/openstack-dev/2017-September/122814.html.
I can console in the amphora and trace the packet is received by my
amphora, but haproxy fails to respond. More details are here
http://lists.openstack.org/pipermail/openstack-dev/2017-September/122587.html.
I think maybe there is something wrong with my latest amphora image, I
hence use an older amphora image in the latest environment, it works. As a
result, the networking are supposed to be fine. What do you think?

Best regards,
Yipei
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171009/eea01992/attachment.html>


More information about the OpenStack-dev mailing list