[2.0-bzr5059] UI reports "Node must be connected to a network" after creating bond

Bug #1588093 reported by Mike Pontillo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Low
Unassigned

Bug Description

Revision history for this message
Andres Rodriguez (andreserl) wrote :

Actually, the message is correct. It is correctly saying that the node should be connected to a network, and this is because no subnet has been selected for the interface.

I think the message should be improved, marking this low!

Changed in maas:
importance: Medium → Low
milestone: none → 2.0.0
Revision history for this message
Mike Pontillo (mpontillo) wrote :

This bug is not about the message being wrong.

The node is already connected to a network. The network link was lost when the two physical interfaces (importantly, both linked to the same network) were converted to a bond.

In order to avoid the issue, we should copy the network link configuration from the primary bond member.

Changed in maas:
milestone: 2.0.0 → 2.3.x
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Revision history for this message
Nishit Goel (nishit2408) wrote :

Hi, I am also facing same issue while compose a machine.

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.