Comment 22 for bug 1618429

Thanks for the configs and logs. It appears to me that it's not running
the newer curtin.
The updated curtin package runs mdadm --assemble --scan -v, which I'm not
seeing in the cloud-init-output.log

If you can obtain the install.log that curtin sends back to maas, I'm told
that's on the Node details page.
Or if you have access to the endpoint, maas configures to write it out to
/tmp/install.log.

That would be the most helpful.

On Tue, Sep 20, 2016 at 1:27 AM, Tytus <email address hidden> wrote:

> ** Attachment added: "cloud-init-output.log"
> https://bugs.launchpad.net/curtin/+bug/1618429/+
> attachment/4744100/+files/cloud-init-output.log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1618429
>
> Title:
> Curtin doesn't clean up previous MD configuration
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1618429/+subscriptions
>