Functional VLAN tagged bonding interfaces are shown as disconnected
Bug #1881901 reported by
Alexander Litvinov
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Unassigned | ||
2.7 |
Fix Committed
|
Medium
|
Heather Lemon | ||
2.8 |
Fix Released
|
Medium
|
Heather Lemon | ||
maas-ui |
Fix Released
|
Unknown
|
Bug Description
After configuring bond and VLAN tagged interfaces on top of it and deploying the server,
VLAN interfaces which are functional, are still shown as disconnected in MAAS UI.
(pls see screenshot)
$ maas root machine get-curtin-config :
https:/
/var/log/maas
https:/
MAAS version: 2.7.1 (8262-g.
Upstream github: https:/
description: | updated |
tags: | added: sts |
description: | updated |
Changed in maas: | |
status: | Triaged → Fix Committed |
Changed in maas: | |
milestone: | none → 2.9.0b1 |
Changed in maas-ui: | |
importance: | Undecided → Unknown |
status: | New → Unknown |
Changed in maas-ui: | |
status: | Unknown → Fix Released |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
It looks like MAAS may be always creating virtual interfaces in a disconnected state as the link speed is unknown
$ maas $PROFILE machine read $SYSTEM_ID | jq -r '.interface_set | .[] | .name + ": " + (.link_ connected| tostring) '
enp1s0: true
enp3s0: true
enp2s0: true
bond0: false
br0: false
MAAS should ensure they are created in a connected state.