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

Bug #1607345 reported by Jason Hobbs on 2016-07-28
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Wishlist
Unassigned
cloud-init
Wishlist
Chad Smith
cloud-init (Ubuntu)
Undecided
Unassigned
Xenial
Undecided
Unassigned
Zesty
Undecided
Unassigned

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.

Related branches

Andres Rodriguez (andreserl) wrote :

MAAS stores install.log.
MAAS doesn't store cloud unit logs because cloud-Init doesn't send them. However, you have rsyslog a that are what cloud-I it logs, although, I think it may not be logging correctly (/var/log/Maas/Rsyslog/)

Changed in maas:
importance: Undecided → Wishlist
milestone: none → next
status: New → Triaged
Changed in maas:
milestone: next → 2.3.0
Joshua Powers (powersj) wrote :

Is there a specific action required by cloud-init here?

Changed in cloud-init:
status: New → Incomplete
Andres Rodriguez (andreserl) wrote :

Yes, curtin sends install.log to MAAS. cloud-init has no feature to send logs back.

Changed in cloud-init:
status: Incomplete → New
Changed in cloud-init:
importance: Undecided → Wishlist
Joshua Powers (powersj) on 2017-08-25
Changed in cloud-init:
status: New → Confirmed
Changed in maas:
milestone: 2.3.0 → 2.3.x
Chad Smith (chad.smith) wrote :

When cloud-init 0.7.10 is released the following command will collect and compress a cloud-initlogs.tgz containing all relevant cloud-init logs:

sudo cloud-init collect-logs [-t <tarfile-path>]

Changed in cloud-init:
assignee: nobody → Chad Smith (chad.smith)
status: Confirmed → In Progress
milestone: none → 0.7.10
Jason Hobbs (jason-hobbs) wrote :

Chad, how will that tie into shipping the logs back to the maas server?

This bug is believed to be fixed in cloud-init in 17.1. If this is still a problem for you, please make a comment and set the state back to New

Thank you.

Changed in cloud-init:
status: In Progress → Fix Released
Brian Murray (brian-murray) wrote :

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.

Changed in cloud-init (Ubuntu Zesty):
status: New → Fix Committed
tags: added: verification-needed verification-needed-zesty

Hello Jason, or anyone else affected,

Accepted cloud-init into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-18-gd4f70470-0ubuntu1~17.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Brian Murray (brian-murray) wrote :

Hello Jason, or anyone else affected,

Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud-init/17.1-18-gd4f70470-0ubuntu1~16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in cloud-init (Ubuntu Xenial):
status: New → Fix Committed
tags: added: verification-needed-xenial
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers