yahoo-eng-team team mailing list archive

[Andres Rodriguez <andreserl@xxxxxxxxxxxxx>]

I'm marking this as incomplete for 2.3 provided that the latest logs
show the failure on 2.3.1. Since 2.3.2 is already released, I'd like to
see if 2.3.2 has improved this.

2018-04-08 10:20:28 provisioningserver.rpc.clusterservice: [info] Rack
controller 'fcffxf' registered (via swoobat:pid=25312) with MAAS version
2.3.1-6470-g036d646-0ubuntu1~16.04.1.

Once we have 2.3.2 runs with this issue, please mark it as 'New'.

** No longer affects: maas/2.4

** Changed in: maas/2.3
    Milestone: None => 2.3.3

** Changed in: maas/2.3
   Importance: Undecided => High

** Changed in: maas/2.3
       Status: New => Incomplete

-- 
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:
  [b1] pod created vm fails commissioning after getting 404 from
  metadata api

Status in cloud-init:
  Invalid
Status in MAAS:
  Triaged
Status in MAAS 2.3 series:
  Incomplete

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