[2.0b8] MTU does not get set on bonded interfaces
Bug #1595755 reported by
Chance Ellis
This bug report is a duplicate of:
Bug #1662948: [2.1, 2.2] MTU of parent device is sometimes set incorrectly.
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
MAAS 2.0 beta 8
When adding a VLAN interface on a bonded interface, the MTU is properly set on the bond.VLAN interface but not properly set on the physical interface members of the bond. This results in the MTU not getting properly set throughout.
summary: |
- MTU does not get set on bonded interfaces + [2.0b8] MTU does not get set on bonded interfaces |
description: | updated |
Changed in maas: | |
milestone: | 2.0.0 → 2.2.0 |
Changed in maas: | |
milestone: | 2.2.0 → 2.2.0rc2 |
To post a comment you must log in.
This looks to be handled correctly in MAAS. Could you please provide the following:
1. Output to command: 'maas {my-maas-session} interfaces read {node-id}'. interfaces' on deployed node.
2. Output to command: 'maas {my-maas-session} machine get-curtin-config {node-id}'
3. Output of '/etc/network/
That will help us determine if its an issue with MAAS not providing the correct information to curtin or that curtin is doing something incorrectly.