Comment 7 for bug 1504265
Revision history for this message
| Juha Tiensyrjä (juha-tiensyrja) wrote | #7 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Thank you, the issue indeed was fixed by setting a correct MTU on the instances via a DHCP option.
We seemed to have hit a bug in (probably) haproxy HTTP mode, which sometimes corrupted some data when the MTU was not correct and fragmentation occurred. We didn't see that behavior when using haproxy LBAAS in TCP mode, but unfortunately I haven't been able to investigate the issue any deeper.