[2.0b8] MTU does not get set on bonded interfaces

Bug #1595755 reported by Chance Ellis
6
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
Revision history for this message
Blake Rouse (blake-rouse) wrote :

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}'.
2. Output to command: 'maas {my-maas-session} machine get-curtin-config {node-id}'
3. Output of '/etc/network/interfaces' on deployed node.

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.

Changed in maas:
status: New → Incomplete
milestone: none → 2.0.0
Revision history for this message
Chance Ellis (chance-ellis) wrote : Re: [Bug 1595755] Re: [2.0b8] MTU does not get set on bonded interfaces

My lab is currently torn down and being moved to a new location. I should have it back up and running sometime over the weekend and can get this info.

Sorry for the delay.

On 6/30/16, 9:36 AM, "Blake Rouse" <<email address hidden> on behalf of <email address hidden>> wrote:

>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}'.
>2. Output to command: 'maas {my-maas-session} machine get-curtin-config {node-id}'
>3. Output of '/etc/network/interfaces' on deployed node.
>
>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.
>
>** Changed in: maas
> Status: New => Incomplete
>
>** Changed in: maas
> Milestone: None => 2.0.0
>
>--
>You received this bug notification because you are subscribed to the bug
>report.
>https://bugs.launchpad.net/bugs/1595755
>
>Title:
> [2.0b8] MTU does not get set on bonded interfaces
>
>Status in MAAS:
> Incomplete
>
>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.
>
>To manage notifications about this bug go to:
>https://bugs.launchpad.net/maas/+bug/1595755/+subscriptions

Changed in maas:
milestone: 2.0.0 → 2.2.0
Changed in maas:
milestone: 2.2.0 → 2.2.0rc2
Revision history for this message
Mike Pontillo (mpontillo) wrote :

I believe this to be fixed in MAAS 2.2.

Marking this a duplicate of bug #1662948.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.