Envs that use tagged interfaces in bonds may loose mtu after reboot due to bug in ubuntu
Bug #1540738 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Confirmed
|
Medium
|
Fuel Sustaining | ||
8.0.x |
Won't Fix
|
Medium
|
MOS Linux | ||
Mitaka |
Won't Fix
|
Medium
|
Fuel Library (Deprecated) |
Bug Description
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:/
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
Changed in fuel: | |
assignee: | nobody → Stanislav Makar (smakar) |
tags: |
added: area-library team-network removed: need-info |
tags: | added: need-info |
Changed in fuel: | |
assignee: | Vladimir Eremin (yottatsa) → Fuel Library Team (fuel-library) |
Changed in fuel: | |
assignee: | Fuel Library (Deprecated) (fuel-library) → Fuel Sustaining (fuel-sustaining-team) |
To post a comment you must log in.
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?