In this guide, we will show you how to:
Collect logs to support your bug report.
File bugs to the upstream
cloud-initproject via GitHub Issues.
Report issues for distro-specific packages.
To aid in debugging, please collect the necessary logs. To do so, run the collect-logs subcommand to produce a tarfile that you can easily upload:
$ sudo cloud-init collect-logs
If your version of
cloud-init does not have the collect-logs
subcommand, then please manually collect the base log files by running the
$ sudo dmesg > dmesg.txt
$ sudo journalctl -o short-precise > journal.txt
$ sudo tar -cvf cloud-init.tar dmesg.txt journal.txt /run/cloud-init \
Report upstream bugs#
Bugs for upstream
cloud-init are tracked using GitHub Issues. To file a
Collect the necessary debug logs as described above.
Report an upstream cloud-init bug on GitHub.
If debug logs are not provided, you will be asked for them before any further time is spent debugging. If you are unable to obtain the required logs please explain why in the bug.
If your bug is for a specific distro using
cloud-init, please first
consider reporting it with the downstream distro or confirm that it still
occurs with the latest upstream
cloud-init code. See the following section
for details on specific distro reporting.
For issues specific to your distro please use one of the following distro-specific reporting mechanisms:
To report a bug on Ubuntu use the ubuntu-bug command on the affected system to automatically collect the necessary logs and file a bug on Launchpad:
$ ubuntu-bug cloud-init
If that does not work or is not an option, please collect the logs using the commands in the above Collect Logs section and then report the bug on the Ubuntu bug tracker. Make sure to attach your collected logs!
Red Hat, CentOS and Fedora#
To file a bug against the Red Hat or Fedora packages of
use the Red Hat bugzilla.
SUSE and openSUSE#
To file a bug against the SUSE packages of
cloud-init please use the