MaaS 3.1 beta 3 "enlist deployed machines" does not capture power configuration, bios_boot_method

Bug #1947901 reported by Ben Huntley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Medium
Unassigned

Bug Description

Following instructions from section "How to update hardware information for a deployed machine" in the MaaS 3.1 beta 3 documentation (https://maas.io/docs/snap/3.1/ui/whats-new-in-maas), and using the OS commissioning script `./maas-run-scripts report-results` for already deployed machines results in a machine with no Power configuration information and no bios_boot_method populated. These machines in-turn cannot be Deployed until these details are set at a later point. The ability to pass missing configuration parameters into `./maas-run-scripts report-results` via args or a yaml file would make the commissioned machines much more useful, as they would now end up with a Deployable configuration. Support to pass in Webhook configuration would in particular be valuable for our use-case.

MaaS region server is running MAAS 3.1.0~beta3 on Ubuntu 20.04, installed from Deb. Rack controller is also running MAAS 3.1.0~beta3 on Ubuntu 20.04. Host being enlisted/comissioned is running Ubuntu 18.04.6.

Revision history for this message
Alberto Donato (ack) wrote :

This is a known limitation of the feature.

Currently MAAS doesn't currently run the bmc-config commissioning script since it potentially modifies the machine setup.

In the future, we plan to extend the feature to collect more information and allow users to provide missing configs, in some way similar to what you describe.

Changed in maas:
status: New → Triaged
milestone: none → next
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers