Comissioning scripts should trigger a hardware reinventory

@kiko,

Is the custom commissioning script enabling the storage being run /before/ the storage discovery script?

Judging by this bug it sounds like it is being run after. Can you confirm that's the case?

That said, this should not be required because you can run custom scripts before MAAS scripts which will yield what you are trying to do without having to re-commission.

Yes, the user-provided commissioning script is running last.

This has the added effect of having hardware testing fail, since it operates on old data (i.e. it thinks there are two drives, but the commissioning script just assembled them into a RAID-1).

Andres, is the workaround for this bug to name the script 00-aa-configure-hba.sh?

The way commissioning scripts have being designed is to allow you to run
the custom script at whatever order, depending on how you name your script.

If you are to name your script to something with "lower priority" than the
MAAS provided, they will be run first, hence, addressing this issue.

On Tue, Jun 6, 2017 at 7:55 PM Christian Reis <email address hidden> wrote:

> Andres, is the workaround for this bug to name the script 00-aa-
> configure-hba.sh?
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1696276
>
> Title:
> Comissioning scripts should trigger a hardware reinventory
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1696276/+subscriptions
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

I believe this is how you would update the name via the API. (I'm on a
plane so can't really verify)

maas <profile>
node-script update <old name>
name=<new name>

On Tue, Jun 6, 2017 at 8:00 PM Andres Rodriguez <email address hidden>
wrote:

> The way commissioning scripts have being designed is to allow you to run
> the custom script at whatever order, depending on how you name your script.
>
> If you are to name your script to something with "lower priority" than the
> MAAS provided, they will be run first, hence, addressing this issue.
>
>
>
> On Tue, Jun 6, 2017 at 7:55 PM Christian Reis <email address hidden> wrote:
>
>> Andres, is the workaround for this bug to name the script 00-aa-
>> configure-hba.sh?
>>
>> --
>> You received this bug notification because you are subscribed to MAAS.
>> https://bugs.launchpad.net/bugs/1696276
>>
>> Title:
>> Comissioning scripts should trigger a hardware reinventory
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/maas/+bug/1696276/+subscriptions
>>
> --
> Andres Rodriguez (RoAkSoAx)
> Ubuntu Server Developer
> MSc. Telecom & Networking
> Systems Engineer
>
--
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

I am trying to think if this bug still makes sense; for instance, if your commissioning script would need to be able to pull the current hardware details from MAAS for it to correctly run. That would imply we probe hardware details twice.. but I don't know if I see a use case.

[Expired for MAAS because there has been no activity for 60 days.]