OK, I didn’t think about it at first.
Commissioning fails at 1st try with default script.
Thing is machine is in « Unconfigured power type » state after that, which is quite annoying, we need to get to manual, then commission again and go to the machine to power it up again.
I’ve toyed with database so 30-maas-01-bmc-config is now default=false and 31-maas-01-bmc-config-custom is default=true in metadataserver_script table.
Now it runs directly the custom script and not 30-maas-01-bmc-config, which is a far better user experience.
Given it’s not a so clean solution, I’d say backporting that patch to 3.3/3.4 would be nice for everyone.
OK, I didn’t think about it at first. 01-bmc- config is now default=false and 31-maas- 01-bmc- config- custom is default=true in metadataserver_ script table. 01-bmc- config, which is a far better user experience.
Commissioning fails at 1st try with default script.
Thing is machine is in « Unconfigured power type » state after that, which is quite annoying, we need to get to manual, then commission again and go to the machine to power it up again.
I’ve toyed with database so 30-maas-
Now it runs directly the custom script and not 30-maas-
Given it’s not a so clean solution, I’d say backporting that patch to 3.3/3.4 would be nice for everyone.
Thanks !