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

Bug #1685615 reported by Mark Shuttleworth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Fix Released
Undecided
Unassigned

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"
Revision history for this message
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?

Revision history for this message
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.

Revision history for this message
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
Revision history for this message
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
Revision history for this message
Björn Tillenius (bjornt) wrote :

I believe that this has been fixed already. Can you please confirm whether this is still a problem in MAAS 2.7?

Changed in maas:
status: Incomplete → New
importance: High → Undecided
assignee: Mike Pontillo (mpontillo) → nobody
milestone: 2.4.x → none
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
Revision history for this message
Mark Shuttleworth (sabdfl) wrote :

Yes, I can confirm this seems to have been fixed at some stage between 2.3 and 2.7.

Changed in maas:
status: Expired → Fix Released
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.