Comment 9 for bug 1742971

Ahh right, we turned on an extra maaslog around the kernel parameters.

On Mon, Mar 26, 2018 at 3:02 PM, Jason Hobbs <email address hidden> wrote:
> I'm sorry, which logs was I supposed to supply?
>
> ** Changed in: maas
> Status: Incomplete => New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1742971
>
> Title:
> [b1] pod created vm fails commissioning after getting 404 from
> metadata api
>
> Status in cloud-init:
> New
> Status in MAAS:
> New
>
> Bug description:
> A vm created via the pods API in maas failed to commission immediately
> after it was created.
>
> It PXE booted, got initrd and the kernel, dhcp'd again, and then
> wasn't heard from anymore:
>
> http://paste.ubuntu.com/26372429/
>
> There are no rsyslog logs for it. The hostname of the vm is
> landscapeamqp-1.maas.
>
> If I connect to the node with virt-viewer, it is sitting at an Ubuntu
> prompt, but I can't login because there are no passwords set. There
> are no console logs available on disk (bug 1742971).
>
> This is with maas 2.3.0 (6434-gd354690-0ubuntu1~16.04.1) in an HA
> setup - logs from the MAAS servers are available in the attached
> infra-logs.tar.
>
> To check for this bug you can look for 404 errors like this:
> http://paste.ubuntu.com/p/hsbw22BFps/
>
>
> This was using the default daily maas images.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1742971/+subscriptions