Envs that use tagged interfaces in bonds may loose mtu after reboot due to bug in ubuntu

[Eugene Nikanorov]

Found on 6.1.
Despite being configured with mtu 9000, that is not applied to a bond after system start if tagged interfaces are used in the bond. That lead to incorrect mtu settings on bridges where the bond is plugged in and so on through the interface chain.

The following bug could be the reason: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1224007

We need to test this for 9.0 and ubuntu version were are installing with the new release.

Not that it doesn't appear each time.

It's not critical since the workaround is to apply mtu settings manually, however it would be good to automate the solution

[Aleksandr Didenko (adidenko)]

8.0 is close to HCF so I've set it to "Won't fix" since it's medium.

Also could you please provide diganostic snapshot or at least astute.yaml from one of the problem nodes?

[Eugene Nikanorov (enikanorov)]

No, I can't provide the snapshot.

The network interface configuration (/etc/*) is correct and was verified by multiple people.
We just need some workaround being installed for ubuntu.
Right now the workaround is to force MTU for the interfaces after reboot via script.

[Dmitry Teselkin (teselkin-d)]

According to comment in upstream component bug [1] this is not a bug in 'ifupdown', but a configuration issue.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722496#10

[Bug Checker Bot (bug-checker)]

(This check performed automatically)
Please, make sure that bug description contains the following sections filled in with the appropriate data related to the bug you are describing:

actual result

expected result

steps to reproduce

For more detailed information on the contents of each of the listed sections see https://wiki.openstack.org/wiki/Fuel/How_to_contribute#Here_is_how_you_file_a_bug

[Dmitry Pyzhov (dpyzhov)]

We passed SCF for 9.0. Moving the medium priority bug to 10.0 release.