← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment

 

This bug is missing the SRU template but I believe this is just adding
an apport hook so I'll let it in without one. However, we should have
one before accepting the package into -updates.

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: cloud-init (Ubuntu Zesty)
       Status: New => Fix Committed

** Tags added: verification-needed verification-needed-zesty

-- 
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/1607345

Title:
  Collect all logs needed to debug curtin/cloud-init for each deployment

Status in cloud-init:
  Fix Released
Status in MAAS:
  Triaged
Status in cloud-init package in Ubuntu:
  New
Status in cloud-init source package in Xenial:
  Fix Committed
Status in cloud-init source package in Zesty:
  Fix Committed

Bug description:
  According to https://bugs.launchpad.net/maas/+bug/1604962/comments/12,
  these logs are needed to debug curtin/cloud-init issues but aren't
  collected automatically by MAAS:

  - /var/log/cloud-init*
  - /run/cloud-init*
  - /var/log/cloud
  - /tmp/install.log

  We need these to be automatically collected by MAAS so we can
  automatically collect them as artifacts in the case of failures in
  OIL.  curtin/cloud-init issues can be race conditions that are
  difficult to reproduce manually, so we need to grab the logs required
  to debug the first time it happens.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1607345/+subscriptions