Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: Add steps to re-run cloud-id and cloud-init #313

Merged
merged 2 commits into from
Apr 10, 2020
Merged

docs: Add steps to re-run cloud-id and cloud-init #313

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
21f4c88
docs: Add steps to re-run cloud-id and cloud-init
Apr 10, 2020
88b7932
Add sudo to commands
Apr 10, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions doc/rtd/topics/faq.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -104,6 +104,23 @@ The force parameter allows the command to be run again since the instance has
already launched. The other options increase the verbosity of logging and
put the logs to STDERR.

How can I re-run datasource detection and cloud-init?
=====================================================

If a user is developing a new datasource or working on debugging an issue it
may be useful to re-run datasource detection and the initial setup of
cloud-init.

To do this, force ds-identify to re-run, clean up any logs, and re-run
cloud-init:

.. code-block:: shell-session

powersj marked this conversation as resolved.
Show resolved Hide resolved
$ sudo DI_LOG=stderr /usr/lib/cloud-init/ds-identify --force
$ sudo cloud-init clean --logs
$ sudo cloud-init init --local
$ sudo cloud-init init

How can I debug my user data?
=============================

Expand Down