[feature] Feedback on LACP bonding status on machine deployment

[Nobuto Murata]

As a wishlist, it would be nice if MAAS feeds back to the user if LACP bonding status is not healthy on machine deployment.

At this moment, LACP bonding can be configured with MAAS cloud metadata and cloud-init, but there is no status check. In case of a mis-cabling or misconfiguration of switches, LACP may report Expired or churned status. Would be nice if MAAS gives that error feedback in the UI or machine status.

[Andres Rodriguez (andreserl)]

Hi Nobuto,

MAAS has no agent running on the machine so it cannot really see issues / status of deployed machines. I'm going to set this as a feature request for when we support / add a agent to a running machine, if any.

[Nobuto Murata (nobuto)]

@Andres, it's true that this is a feature request. The LACP bonding status check may not require an agent since I'm fine with one-time check like reporting cloud-init failures you implemented before:
https://bugs.launchpad.net/maas/+bug/1707850
(or we could use cloud-init to enable bonding status check at the end of network configuration.)

[Adam Collard (adam-collard)]

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