Public bug reported: 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. This was using the default daily maas images. ** Affects: cloud-init Importance: Undecided Status: New ** Affects: maas Importance: Undecided Status: New ** Tags: cdo-qa cdo-qa-blocker foundations-engine ** Attachment added: "infra-logs.tar" https://bugs.launchpad.net/bugs/1742971/+attachment/5035884/+files/infra-logs.tar ** Tags removed: cpe-foundations ** Tags added: foundations-engine ** Also affects: cloud-init Importance: Undecided Status: New ** Description changed: A vm created via the pods API in maas failed to commission. 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. 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 + logs.tar. + + This was using the default daily maas images. ** Description changed: - A vm created via the pods API in maas failed to commission. + 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. This was using the default daily maas images. -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to cloud-init. https://bugs.launchpad.net/bugs/1742971 Title: pod created vm fails commissioning after apparently booting to linux 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. 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 -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp