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

[ubuntu-server-builder]

This bug was originally filed in Launchpad as LP: #1607345

Launchpad details

affected_projects = ['maas', 'cloud-init (Ubuntu)', 'cloud-init (Ubuntu Xenial)', 'cloud-init (Ubuntu Zesty)']
assignee = None
assignee_name = None
date_closed = None
date_created = 2016-07-28T12:09:15.169555+00:00
date_fix_committed = None
date_fix_released = None
id = 1607345
importance = medium
is_complete = False
lp_url = https://bugs.launchpad.net/cloud-init/+bug/1607345
milestone = 0.7.10
owner = andreserl
owner_name = Andres Rodriguez
private = False
status = confirmed
submitter = jason-hobbs
submitter_name = Jason Hobbs
tags = ['cdo-qa', 'foundations-engine', 'oil', 'verification-done', 'verification-done-xenial', 'verification-done-zesty']
duplicates = [1691765, 1774202]

Launchpad user Jason Hobbs(jason-hobbs) wrote on 2016-07-28T12:09:15.169555+00:00

Re-opening this bug as confirmed because the previous SRU content released only provided only 'cloud-init collect-logs'. A command line tool which tars all cloud-init install logs and artifacts for triage.

However, those fixes did not provide any configuration options for MAAS to request that those logs are automatically published to MAAS upon error.

Cloud-init should provide cloud-config which allows consumers to specify an endpoint and oauth credentials to which cloud-init will automatically POST all compressed cloud-init log artifacts.

=== Original 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.

=== Begin SRU Template === [Impact] ubuntu-bug cloud-init now collects cloud-init-related information for a bug-report

[Test Case]

Launch instance under test

$ for release in xenial zesty;   do     ref=$release-proposed;     lxc-proposed-snapshot --proposed --publish $release $ref;     lxc launch $ref $name;     sleep 10;     lxc exec $name ubuntu-bug cloud-init # And follow the prompts to report a bogus bug   done

[Regression Potential] Worst case scenario is the apport wrapper doesn't work and the developer has to file a bug manually instead.

[Other Info] Upstream commit at   https://git.launchpad.net/cloud-init/commit/?id=ca2730e2ac86b05f7e6

=== End SRU Template ===

[ubuntu-server-builder]

Launchpad user Andres Rodriguez(andreserl) wrote on 2016-07-28T12:18:29.939054+00:00

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

[ubuntu-server-builder]

Launchpad user Joshua Powers(powersj) wrote on 2017-07-28T22:24:05.270991+00:00

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

[ubuntu-server-builder]

Launchpad user Andres Rodriguez(andreserl) wrote on 2017-07-29T11:40:31.326348+00:00

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

[ubuntu-server-builder]

Launchpad user Chad Smith(chad.smith) wrote on 2017-09-14T04:16:16.600118+00:00

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 ]

[ubuntu-server-builder]

Launchpad user Jason Hobbs(jason-hobbs) wrote on 2017-09-14T12:38:30.051205+00:00

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

[ubuntu-server-builder]

Launchpad user Scott Moser(smoser) wrote on 2017-09-23T02:13:52.172023+00:00

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.

[ubuntu-server-builder]

Launchpad user Brian Murray(brian-murray) wrote on 2017-10-12T20:55:34.303928+00:00

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.

[ubuntu-server-builder]

Launchpad user Brian Murray(brian-murray) wrote on 2017-10-12T20:57:18.618240+00:00

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!

[ubuntu-server-builder]

Launchpad user Brian Murray(brian-murray) wrote on 2017-10-12T21:04:46.329651+00:00

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!

[ubuntu-server-builder]

Launchpad user Brian Murray(brian-murray) wrote on 2017-10-19T18:11:14.427045+00:00

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.2 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!

[ubuntu-server-builder]

Launchpad user Brian Murray(brian-murray) wrote on 2017-10-19T18:14:54.096117+00:00

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.2 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!

[ubuntu-server-builder]

Launchpad user Chris Halse Rogers(raof) wrote on 2017-10-25T03:20:13.649120+00:00

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-25-g17a15f9e-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!

[ubuntu-server-builder]

Launchpad user Chris Halse Rogers(raof) wrote on 2017-10-25T03:29:01.822665+00:00

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-25-g17a15f9e-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!

[ubuntu-server-builder]

Launchpad user Chad Smith(chad.smith) wrote on 2017-10-25T16:18:45.086538+00:00

=== cloud-init SRU Verification output === --- xenial root@test-xenial:~# ubuntu-bug cloud-init

*** Collecting problem information

The collected information can be sent to the developers to improve the application. This might take a few minutes. ............. *** Your device details (lshw) may be useful to developers when addressing this bug, but gathering it requires admin privileges. Would you like to include this info?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y

*** Is this machine running in a cloud environment?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y

*** Please select the cloud vendor or environment in which this instance is running

Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 6 . *** Your user-data or cloud-config file can optionally be provided from /var/lib/cloud/instance/user-data.txt and could be useful to developers when addressing this bug. Do you wish to attach user-data to this bug?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y ..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the automatically opened web browser.

What would you like to do? Your options are: S: Send report (85.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v

What would you like to do? Your options are: S: Send report (85.6 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): k Problem report file: /tmp/apport.cloud-init.7_ilbqj5.apport

root@test-xenial:~# egrep 'user_data|Cloud|lshw' /tmp/apport.cloud-init.7_ilbqj5.apport CloudName: CloudSigma Cloud-init v. 17.1 running 'init-local' at Mon, 16 Oct 2017 20:21:45 +0000. Up 0.00 seconds. Cloud-init v. 17.1 running 'init' at Mon, 16 Oct 2017 20:21:49 +0000. Up 4.00 seconds. Cloud-init v. 17.1 running 'modules:config' at Mon, 16 Oct 2017 20:21:50 +0000. Up 5.00 seconds. Cloud-init v. 17.1 running 'modules:final' at Mon, 16 Oct 2017 20:21:51 +0000. Up 6.00 seconds. Cloud-init v. 17.1 finished at Mon, 16 Oct 2017 20:22:26 +0000. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 41.00 seconds lshw.txt: user_data.txt:

---zesty root@test-zesty:~# ubuntu-bug cloud-init

*** Collecting problem information

The collected information can be sent to the developers to improve the application. This might take a few minutes. ............ *** Your device details (lshw) may be useful to developers when addressing this bug, but gathering it requires admin privileges. Would you like to include this info?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y

*** Is this machine running in a cloud environment?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y

*** Please select the cloud vendor or environment in which this instance is running

Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 5

*** Your user-data or cloud-config file can optionally be provided from /var/lib/cloud/instance/user-data.txt and could be useful to developers when addressing this bug. Do you wish to attach user-data to this bug?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y ..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the automatically opened web browser.

What would you like to do? Your options are: S: Send report (102.7 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): k Problem report file: /tmp/apport.cloud-init.c2rk91_3.apport root@test-zesty:~# egrep 'user_data|cloud|lshw' /tmp/apport.cloud-init.c2rk91_3.apport cloud-guest-utils 0.30-0ubuntu2 Oct 16 20:25:24 hostname systemd[1]: cloud-init-local.service: Failed to reset devices.list: Operation not permitted Oct 16 20:25:24 hostname systemd[1]: cloud-init-local.service: Failed to set invocation ID on control group /system.slice/cloud-init-local.service, ignoring: Operation not permitted Oct 16 20:25:24 hostname systemd[1]: cloud-init-local.service: Failed to reset devices.list: Operation not permitted Oct 16 20:25:24 hostname systemd[1]: cloud-init-local.service: Failed to set invocation ID on control group /system.slice/cloud-init-local.service, ignoring: Operation not permitted Oct 16 20:25:28 hostname systemd[1]: cloud-init.service: Failed to reset devices.list: Operation not permitted Oct 16 20:25:28 hostname systemd[1]: cloud-init.service: Failed to set invocation ID on control group /system.slice/cloud-init.service, ignoring: Operation not permitted Oct 16 20:25:28 hostname systemd[1]: cloud-init-local.service: Failed to reset devices.list: Operation not permitted Oct 16 20:25:28 hostname systemd[1]: cloud-init-local.service: Failed to set invocation ID on control group /system.slice/cloud-init-local.service, ignoring: Operation not permitted Oct 16 20:25:29 hostname systemd[1]: cloud-config.service: Failed to reset devices.list: Operation not permitted Oct 16 20:25:29 hostname systemd[1]: cloud-config.service: Failed to set invocation ID on control group /system.slice/cloud-config.service, ignoring: Operation not permitted Oct 16 20:25:31 hostname systemd[1]: cloud-final.service: Failed to reset devices.list: Operation not permitted Oct 16 20:25:31 hostname systemd[1]: cloud-final.service: Failed to set invocation ID on control group /system.slice/cloud-final.service, ignoring: Operation not permitted Oct 16 20:25:31 hostname systemd[1]: cloud-config.service: Failed to reset devices.list: Operation not permitted Oct 16 20:25:31 hostname systemd[1]: cloud-config.service: Failed to set invocation ID on control group /system.slice/cloud-config.service, ignoring: Operation not permitted Package: cloud-init 17.1-18-gd4f70470-0ubuntu1~17.04.1

egrep 'user_data|Cloud|lshw' /tmp/apport.cloud-init.c2rk91_3.apport CloudName: Bigstep Cloud-init v. 17.1 running 'init-local' at Mon, 16 Oct 2017 20:25:24 +0000. Up 0.00 seconds. Cloud-init v. 17.1 running 'init' at Mon, 16 Oct 2017 20:25:28 +0000. Up 4.00 seconds. Cloud-init v. 17.1 running 'modules:config' at Mon, 16 Oct 2017 20:25:30 +0000. Up 6.00 seconds. Cloud-init v. 17.1 running 'modules:final' at Mon, 16 Oct 2017 20:25:31 +0000. Up 7.00 seconds. Cloud-init v. 17.1 finished at Mon, 16 Oct 2017 20:26:07 +0000. Datasource DataSourceNoCloud [seed=/var/lib/cloud/seed/nocloud-net][dsmode=net]. Up 43.00 seconds lshw.txt: user_data.txt:

=== End SRU Verification output ===

[ubuntu-server-builder]

Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-11-07T17:07:16.548527+00:00

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-27-geb292c18-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!

[ubuntu-server-builder]

Launchpad user Łukasz Zemczak(sil2100) wrote on 2017-11-07T17:17:41.096785+00:00

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-27-geb292c18-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!

[ubuntu-server-builder]

Launchpad user Chad Smith(chad.smith) wrote on 2017-11-07T19:49:40.599774+00:00

=== abridged SRU Verification output === for release in xenial zesty;

do ref=$release-proposed; name=test-$release; lxc-proposed-snapshot --proposed --publish $release $ref; lxc launch $ref $name; sleep 10; lxc exec $name ubuntu-bug cloud-init done Creating xenial-proposed-232735567 [sudo] password for csmith: --proposed -- ... The following packages will be upgraded: cloud-init Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 cloud-init all 17.1-27-geb292c18-0ubuntu1~16.04.1 [341 kB] ... Starting test-xenial

*** Collecting problem information

The collected information can be sent to the developers to improve the application. This might take a few minutes. ..................... *** Your device details (lshw) may be useful to developers when addressing this bug, but gathering it requires admin privileges. Would you like to include this info?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y

*** Is this machine running in a cloud environment?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y

*** Please select the cloud vendor or environment in which this instance is running

Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 4 . *** Your user-data or cloud-config file can optionally be provided from /var/lib/cloud/instance/user-data.txt and could be useful to developers when addressing this bug. Do you wish to attach user-data to this bug?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y ..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the automatically opened web browser.

What would you like to do? Your options are: S: Send report (79.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v

What would you like to do? Your options are: S: Send report (79.1 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): c --- zesty Creating zesty-proposed-2228631772 --proposed -- The following packages will be upgraded: cloud-init ... Get:1 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 cloud-init all 17.1-27-geb292c18-0ubuntu1~17.04.1 [339 kB] ... Starting test-zesty

*** Collecting problem information

The collected information can be sent to the developers to improve the application. This might take a few minutes. ..................... *** Your device details (lshw) may be useful to developers when addressing this bug, but gathering it requires admin privileges. Would you like to include this info?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y PCI (sysfs)

*** Is this machine running in a cloud environment?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y

*** Please select the cloud vendor or environment in which this instance is running

Choices: 1: Amazon - Ec2 2: AliYun 3: AltCloud 4: Azure 5: Bigstep 6: CloudSigma 7: CloudStack 8: DigitalOcean 9: GCE - Google Compute Engine 10: MAAS 11: NoCloud 12: OpenNebula 13: OpenStack 14: OVF 15: Scaleway 16: SmartOS 17: VMware 18: Other C: Cancel Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 8

*** Your user-data or cloud-config file can optionally be provided from /var/lib/cloud/instance/user-data.txt and could be useful to developers when addressing this bug. Do you wish to attach user-data to this bug?

What would you like to do? Your options are: Y: Yes N: No C: Cancel Please choose (Y/N/C): y ..

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the automatically opened web browser.

What would you like to do? Your options are: S: Send report (86.8 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): v

What would you like to do? Your options are: S: Send report (86.8 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): c

=== End SRU Verification output ===

[ubuntu-server-builder]

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-14T22:23:59.287002+00:00

This bug was fixed in the package cloud-init - 17.1-27-geb292c18-0ubuntu1~17.04.1

---

cloud-init (17.1-27-geb292c18-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

• New upstream snapshot.
  • EC2: Limit network config to fallback nic, fix local-ipv4 only instances. (LP: #1728152)
  • Gentoo: Use "rc-service" rather than "service". [Carlos Konstanski]

cloud-init (17.1-25-g17a15f9e-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

• New upstream snapshot.
  • resizefs: Fix regression when system booted with root=PARTUUID= (LP: #1725067)
  • tools: make yum package installation more reliable
  • citest: fix remaining warnings raised by integration tests.
  • citest: show the class actual class name in results.
  • ntp: fix config module schema to allow empty ntp config (LP: #1724951)
  • tools: disable fastestmirror if using proxy [Joshua Powers]

cloud-init (17.1-18-gd4f70470-0ubuntu1~17.04.2) zesty-proposed; urgency=medium

• cherry-pick 41152f1: schema: Log debug instead of warning when jsonschema is absent (LP: #1724354)

cloud-init (17.1-18-gd4f70470-0ubuntu1~17.04.1) zesty-proposed; urgency=medium

• drop the following cherry picks, now incorporated in snapshot.
  • debian/patches/cpick-a2f8ce9c-Do-not-provide-systemd-fsck-drop...
• debian/copyright: dep5 updates, reorganize, add Apache 2.0 license. (LP: #1718681)
• debian/control: drop dependency on python3-prettytable
• debian/rules: install rsyslog file with 0644 mode instead of 0755.
• debian/rules, debian/apport-launcher.py: add an apport hook. (LP: #1607345)

• New upstream snapshot (LP: #1721847)

  • simpletable: Fix get_string method to return table-formatted string
  • net: Handle bridge stp values of 0 and convert to boolean type [Chad Smith]
  • tools: Give specific --abbrev=8 to "git describe"
  • network: bridge_stp value not always correct [Ryan Harper]
  • tests: re-enable tox with nocloud-kvm support [Joshua Powers]
  • systemd: remove limit on tasks created by cloud-init-final.service. [Robert Schweikert]
  • suse: Support addition of zypper repos via cloud-config. [Robert Schweikert]
  • tests: Combine integration configs and testcases [Joshua Powers]
  • Azure, CloudStack: Support reading dhcp options from systemd-networkd. [Dimitri John Ledkov]
  • packages/debian/copyright: remove mention of boto and MIT license
  • systemd: only mention Before=apt-daily.service on debian based distros. [Robert Schweikert]
  • Add missing simpletable and simpletable tests for failed merge [Chad Smith]
  • Remove prettytable dependency, introduce simpletable [Andrew Jorgensen]
  • debian/copyright: dep5 updates, reorganize, add Apache 2.0 license. [Joshua Powers]
  • tests: remove dependency on shlex [Joshua Powers]
  • AltCloud: Trust PATH for udevadm and modprobe.
  • DataSourceOVF: use util.find_devs_with(TYPE=iso9660) [Ryan Harper]
  • tests: remove a temp file used in bootcmd tests.
  • release 17.1
  • doc: document GCE datasource. [Arnd Hannemann]
  • suse: updates to templates to support openSUSE and SLES. [Robert Schweikert]
  • suse: Copy sysvinit files from redhat with slight changes. [Robert Schweikert]
  • docs: fix sphinx module schema documentation [Chad Smith]
  • tests: Add cloudinit package to all test targets [Chad Smith]
  • Makefile: No longer look for yaml files in obsolete ./bin/.
  • tests: fix ds-identify unit tests to set EC2_STRICT_ID_DEFAULT.
  • ec2: Fix maybe_perform_dhcp_discovery to use /var/tmp as a tmpdir [Chad Smith]
  • Azure: wait longer for SSH pub keys to arrive. [Paul Meyer]
  • GCE: Fix usage of user-data.
  • cmdline: add collect-logs subcommand. [Chad Smith]
  • CloudStack: consider dhclient lease files named with a hyphen.
  • resizefs: Drop check for read-only device file, do not warn on overlayroot. [Chad Smith]
  • tests: Enable the NoCloud KVM platform [Joshua Powers]
  • resizefs: pass mount point to xfs_growfs [Dusty Mabe]
  • vmware: Enable nics before sending the SUCCESS event. [Sankar Tanguturi]
  • cloud-config modules: honor distros definitions in each module [Chad Smith]
  • chef: Add option to pin chef omnibus install version [Ethan Apodaca]
  • tests: execute: support command as string [Joshua Powers]
  • schema and docs: Add jsonschema to resizefs and bootcmd modules [Chad Smith]
  • tools: Add xkvm script, wrapper around qemu-system [Joshua Powers]
  • vmware customization: return network config format [Sankar Tanguturi]
  • Ec2: only attempt to operate at local mode on known platforms.
  • Use /run/cloud-init for tempfile operations.
  • ds-identify: Make OpenStack return maybe on arch other than intel.
  • tests: mock missed openstack metadata uri network_data.json [Chad Smith]
  • relocate tests/unittests/helpers.py to cloudinit/tests [Lars Kellogg-Stedman]
  • tox: add nose timer output [Joshua Powers]
  • upstart: do not package upstart jobs, drop ubuntu-init-switch module.
  • tests: Stop leaking calls through unmocked metadata addresses [Chad Smith]
  • distro: allow distro to specify a default locale [Ryan Harper]
  • tests: fix two recently added tests for sles distro.
  • url_helper: dynamically import oauthlib import from inside oauth_headers [Chad Smith]
  • tox: make xenial environment run with python3.6
  • suse: Add support for openSUSE and return SLES to a working state. [Robert Schweikert]
  • GCE: Add a main to the GCE Datasource.
  • ec2: Add IPv6 dhcp support to Ec2DataSource. [Chad Smith]
  • url_helper: fail gracefully if oauthlib is not available [Lars Kellogg-Stedman]
  • cloud-init analyze: fix issues running under python 2. [Andrew Jorgensen]
  • Configure logging module to always use UTC time. [Ryan Harper]
  • Log a helpful message if a user script does not include shebang. [Andrew Jorgensen]
  • cli: Fix command line parsing of coniditionally loaded subcommands. [Chad Smith]
  • doc: Explain error behavior in user data include file format. [Jason Butz]
  • cc_landscape & cc_puppet: Fix six.StringIO use in writing configs [Chad Smith]
  • schema cli: Add schema subcommand to cloud-init cli and cc_runcmd schema [Chad Smith]
  • Debian: Remove non-free repositories from apt sources template. [Joonas Kylmälä]
  • tools: Add tooling for basic cloud-init performance analysis. [Chad Smith]
  • network: add v2 passthrough and fix parsing v2 config with bonds/bridge params [Ryan Harper]
  • doc: update capabilities with features available, link doc reference, cli example [Ryan Harper]
  • vcloud directory: Guest Customization support for passwords [Maitreyee Saikia]
  • ec2: Allow Ec2 to run in init-local using dhclient in a sandbox. [Chad Smith]
  • cc_ntp: fallback on timesyncd configuration if ntp is not installable [Ryan Harper]
  • net: Reduce duplicate code. Have get_interfaces_by_mac use get_interfaces.
  • tests: Fix build tree integration tests [Joshua Powers]
  • sysconfig: Dont repeat header when rendering resolv.conf [Ryan Harper]
  • archlinux: Fix bug with empty dns, do not render 'lo' devices.

  -- Chad Smith chad.smith@canonical.com Tue, 31 Oct 2017 13:08:43 -0600

[ubuntu-server-builder]

Launchpad user Brian Murray(brian-murray) wrote on 2017-11-14T22:24:14.161519+00:00

The verification of the Stable Release Update for cloud-init has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[ubuntu-server-builder]

Launchpad user Launchpad Janitor(janitor) wrote on 2017-11-15T01:07:42.077466+00:00

This bug was fixed in the package cloud-init - 17.1-27-geb292c18-0ubuntu1~16.04.1

---

cloud-init (17.1-27-geb292c18-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

• New upstream snapshot.
  • EC2: Limit network config to fallback nic, fix local-ipv4 only instances. (LP: #1728152)
  • Gentoo: Use "rc-service" rather than "service". [Carlos Konstanski]

cloud-init (17.1-25-g17a15f9e-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

• New upstream snapshot.
  • resizefs: Fix regression when system booted with root=PARTUUID= (LP: #1725067)
  • tools: make yum package installation more reliable
  • citest: fix remaining warnings raised by integration tests.
  • citest: show the class actual class name in results.
  • ntp: fix config module schema to allow empty ntp config (LP: #1724951)
  • tools: disable fastestmirror if using proxy [Joshua Powers]

cloud-init (17.1-18-gd4f70470-0ubuntu1~16.04.2) xenial-proposed; urgency=medium

• cherry-pick 41152f1: schema: Log debug instead of warning when jsonschema is absent (LP: #1724354)

cloud-init (17.1-18-gd4f70470-0ubuntu1~16.04.1) xenial-proposed; urgency=medium

• drop the following cherry picks, now incorporated in snapshot.
  • debian/patches/cpick-a2f8ce9c-Do-not-provide-systemd-fsck-drop...
• debian/copyright: dep5 updates, reorganize, add Apache 2.0 license. (LP: #1718681)
• debian/control: drop dependency on python3-prettytable
• debian/rules: install rsyslog file with 0644 mode instead of 0755.
• debian/rules, debian/apport-launcher.py: add an apport hook. (LP: #1607345)

• New upstream snapshot. (LP: #1721847)

  • simpletable: Fix get_string method to return table-formatted string
  • net: Handle bridge stp values of 0 and convert to boolean type [Chad Smith]
  • tools: Give specific --abbrev=8 to "git describe"
  • network: bridge_stp value not always correct [Ryan Harper]
  • tests: re-enable tox with nocloud-kvm support [Joshua Powers]
  • systemd: remove limit on tasks created by cloud-init-final.service. [Robert Schweikert]
  • suse: Support addition of zypper repos via cloud-config. [Robert Schweikert]
  • tests: Combine integration configs and testcases [Joshua Powers]
  • Azure, CloudStack: Support reading dhcp options from systemd-networkd. [Dimitri John Ledkov]
  • packages/debian/copyright: remove mention of boto and MIT license
  • systemd: only mention Before=apt-daily.service on debian based distros. [Robert Schweikert]
  • Add missing simpletable and simpletable tests for failed merge [Chad Smith]
  • Remove prettytable dependency, introduce simpletable [Andrew Jorgensen]
  • debian/copyright: dep5 updates, reorganize, add Apache 2.0 license. [Joshua Powers]
  • tests: remove dependency on shlex [Joshua Powers]
  • AltCloud: Trust PATH for udevadm and modprobe.
  • DataSourceOVF: use util.find_devs_with(TYPE=iso9660) [Ryan Harper]
  • tests: remove a temp file used in bootcmd tests.
  • release 17.1
  • doc: document GCE datasource. [Arnd Hannemann]
  • suse: updates to templates to support openSUSE and SLES. [Robert Schweikert]
  • suse: Copy sysvinit files from redhat with slight changes. [Robert Schweikert]
  • docs: fix sphinx module schema documentation [Chad Smith]
  • tests: Add cloudinit package to all test targets [Chad Smith]
  • Makefile: No longer look for yaml files in obsolete ./bin/.
  • tests: fix ds-identify unit tests to set EC2_STRICT_ID_DEFAULT.
  • ec2: Fix maybe_perform_dhcp_discovery to use /var/tmp as a tmpdir [Chad Smith]
  • Azure: wait longer for SSH pub keys to arrive. [Paul Meyer]
  • GCE: Fix usage of user-data.
  • cmdline: add collect-logs subcommand. [Chad Smith]
  • CloudStack: consider dhclient lease files named with a hyphen.
  • resizefs: Drop check for read-only device file, do not warn on overlayroot. [Chad Smith]
  • tests: Enable the NoCloud KVM platform [Joshua Powers]
  • resizefs: pass mount point to xfs_growfs [Dusty Mabe]
  • vmware: Enable nics before sending the SUCCESS event. [Sankar Tanguturi]
  • cloud-config modules: honor distros definitions in each module [Chad Smith]
  • chef: Add option to pin chef omnibus install version [Ethan Apodaca]
  • tests: execute: support command as string [Joshua Powers]
  • schema and docs: Add jsonschema to resizefs and bootcmd modules [Chad Smith]
  • tools: Add xkvm script, wrapper around qemu-system [Joshua Powers]
  • vmware customization: return network config format [Sankar Tanguturi]
  • Ec2: only attempt to operate at local mode on known platforms.
  • Use /run/cloud-init for tempfile operations.
  • ds-identify: Make OpenStack return maybe on arch other than intel.
  • tests: mock missed openstack metadata uri network_data.json [Chad Smith]
  • relocate tests/unittests/helpers.py to cloudinit/tests [Lars Kellogg-Stedman]
  • tox: add nose timer output [Joshua Powers]
  • upstart: do not package upstart jobs, drop ubuntu-init-switch module.
  • tests: Stop leaking calls through unmocked metadata addresses [Chad Smith]
  • distro: allow distro to specify a default locale [Ryan Harper]
  • tests: fix two recently added tests for sles distro.
  • url_helper: dynamically import oauthlib import from inside oauth_headers [Chad Smith]
  • tox: make xenial environment run with python3.6
  • suse: Add support for openSUSE and return SLES to a working state. [Robert Schweikert]
  • GCE: Add a main to the GCE Datasource.
  • ec2: Add IPv6 dhcp support to Ec2DataSource. [Chad Smith]
  • url_helper: fail gracefully if oauthlib is not available [Lars Kellogg-Stedman]
  • cloud-init analyze: fix issues running under python 2. [Andrew Jorgensen]
  • Configure logging module to always use UTC time. [Ryan Harper]
  • Log a helpful message if a user script does not include shebang. [Andrew Jorgensen]
  • cli: Fix command line parsing of coniditionally loaded subcommands. [Chad Smith]
  • doc: Explain error behavior in user data include file format. [Jason Butz]
  • cc_landscape & cc_puppet: Fix six.StringIO use in writing configs [Chad Smith]
  • schema cli: Add schema subcommand to cloud-init cli and cc_runcmd schema [Chad Smith]
  • Debian: Remove non-free repositories from apt sources template. [Joonas Kylmälä]
  • tools: Add tooling for basic cloud-init performance analysis. [Chad Smith]
  • network: add v2 passthrough and fix parsing v2 config with bonds/bridge params [Ryan Harper]
  • doc: update capabilities with features available, link doc reference, cli example [Ryan Harper]
  • vcloud directory: Guest Customization support for passwords [Maitreyee Saikia]
  • ec2: Allow Ec2 to run in init-local using dhclient in a sandbox. [Chad Smith]
  • cc_ntp: fallback on timesyncd configuration if ntp is not installable [Ryan Harper]
  • net: Reduce duplicate code. Have get_interfaces_by_mac use get_interfaces.
  • tests: Fix build tree integration tests [Joshua Powers]
  • sysconfig: Dont repeat header when rendering resolv.conf [Ryan Harper]
  • archlinux: Fix bug with empty dns, do not render 'lo' devices.

  -- Chad Smith chad.smith@canonical.com Tue, 31 Oct 2017 13:10:51 -0600

[ubuntu-server-builder]

Launchpad user Andres Rodriguez(andreserl) wrote on 2018-05-31T19:55:38.089580+00:00

For the wider audience, this issue has not really been fixed in cloud-init for MAAS to be able to use it to collect logs. SO cloud-init needs to address this before MAAS can start collecting logs.

[ubuntu-server-builder]

Launchpad user Andres Rodriguez(andreserl) wrote on 2018-05-31T20:00:44.223719+00:00

Marking as incomplete for MAAS for the lack of a better status until cloud-init supports sending logs back, so that it is not confused with the cloud-init status.

[ubuntu-server-builder]

Launchpad user Björn Tillenius(bjornt) wrote on 2019-01-11T09:09:27.624170+00:00

Can someone please reopen this for cloud-init, since the fix wasn't the right one?

[ubuntu-server-builder]

Launchpad user Chad Smith(chad.smith) wrote on 2019-03-14T20:23:49.628657+00:00

Cloud-init will likely need a couple of fixes to support this feature:

• A new reporting handler which will POST collected cloud-init logs on cloud-init failure/exception conditions

• Add #cloud-config support for reporting: opaquekey_maas_errorlogs: type: postlogs endpoint: http://yourendpoint consumer_key: con_key token_key: tk_key token_secret: tk_secret

[ubuntu-server-builder]

Launchpad user Adam Collard(adam-collard) wrote on 2019-09-19T11:51:57.360893+00:00

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

[holmanb]

This is believed to be implemented in cloud-init via event reporting. Closing.