Comment 1 for bug 2018998
Revision history for this message
| Pedro Victor Lourenço Fragola (pedrovlf) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
I had the same situation when the lb-mgmt-net was set to use 9042 MTU and o-hm0 is set to use 1500 MTU.
The Octavia units will show the drop packets:
[2065317.692684] o-hm0: dropped over-mtu packet: 1744 > 1500
[2065339.573539] o-hm0: dropped over-mtu packet: 1654 > 1500
[2065347.747633] o-hm0: dropped over-mtu packet: 1744 > 1500
[2065375.092206] o-hm0: dropped over-mtu packet: 1653 > 1500
[2065405.176370] o-hm0: dropped over-mtu packet: 1655 > 1500
If the lb-mgmt-net is set to use the same MTU as o-hm0, for example, 1500 it will work using defragment.
During the problem, Octavia Health starts the failover of the amphoras after 60 seconds.
In this case, the LB has more than 60 members.
[Workaround]
The workaround described on this LP works, but the final solution would be the charm check the MTU config lb-mgmt-net and set the same config for o-hm0 interface.