[2.2] Bonded interfaces on a controller or device are shown as "Unconfigured"

Bug #1685615 reported by Mark Shuttleworth on 2017-04-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Mike Pontillo

Bug Description

I have a controller with two bonded NIcs, but the display in MAAS shows those interfaces as "Unconfigured".

Changed in maas:
status: New → Triaged
importance: Undecided → Critical
milestone: none → 2.2.0rc3
Changed in maas:
assignee: nobody → Mike Pontillo (mpontillo)
summary: - Bonded interfaces on a controller or device are shown as "Unconfigured"
+ [2.2] Bonded interfaces on a controller or device are shown as
+ "Unconfigured"
Mike Pontillo (mpontillo) wrote :

I'm going to try to reproduce this issue, but if you get a chance, could you please attach the output of:

    sudo maas-rack support-dump --networking

... and let me know which specific interfaces are displayed incorrectly?

Mike Pontillo (mpontillo) wrote :

I've not been able to get this to happen in my MAAS test setups; MAAS is properly showing the controller's bond interface on its details page. (see attached screenshot)

Could you attach more details, such as the support dump requested above, and any other information that might be relevant about how the interface is configured? (what does /e/n/i look like, etc.) Then we can write a better test case for this.

Mike Pontillo (mpontillo) wrote :

I'm worried that this is related to bug #1685306, where a machine interface suddenly becomes unconfigured just as it is deployed. I'm going to dig into that one to see if I can find a connection.

Changed in maas:
status: Triaged → Incomplete
Mike Pontillo (mpontillo) wrote :

Can you also test if this is HA related? That is, if you have multiple rack controllers, shut the secondary down and check if the issue still occurs on the controller that remains online.

Changed in maas:
milestone: 2.2.0rc3 → 2.2.1
Changed in maas:
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Changed in maas:
milestone: 2.2.1 → 2.2.x
Changed in maas:
milestone: 2.2.x → 2.3.0
Changed in maas:
milestone: 2.3.0 → 2.3.x
Changed in maas:
importance: Critical → High
milestone: 2.3.x → 2.4.x
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers