~lp-markusschade/cloud-init:migrate-lp-to-github

Last commit made on 2020-10-26
Get this branch:
git clone -b migrate-lp-to-github https://git.launchpad.net/~lp-markusschade/cloud-init
Only Markus Schade can upload to this branch. If you are Markus Schade please log in for upload directions.

Branch merges

Branch information

Name:
migrate-lp-to-github
Repository:
lp:~lp-markusschade/cloud-init

Recent commits

fb2c5f1... by Markus Schade

lp-to-git-users: adding asciiprod

Mapped from lp-markusschade

f5b3ad7... by Dan Watkins

stages: don't reset permissions of cloud-init.log every boot (#624)

ensure_file needed modification to support doing this, so this commit
also includes the following changes:

test_util: add tests for util.ensure_file
util: add preserve_mode parameter to ensure_file
util: add (partial) type annotations to ensure_file

LP: #1900837

72d85ff... by Joshua Powers

docs: Add how to use cloud-localds to boot qemu (#617)

* docs: Add hot to use cloud-localds to boot qemu

There is a complete lack of documentation on using cloud-localds with
cloud-init to boot an image locally.

Drive by, added some more whitepapers, blogs, and videos

* fix line length

* * add where cloud-localds comes from
* add more specific example with metadata and network config

* Add link to cloud-utils package

93cebe0... by Scott Moser

Drop vestigial update_resolve_conf_file function (#620)

update_resolve_conf_file is no longer used. The last reference
to it was removed in c3680475f9c970, which was itself a "remove dead
code" commit.

5f8a2bb... by Dan Watkins

cc_mounts: correctly fallback to dd if fallocate fails (#585)

`create_swap()` was previously catching and not re-raising the
ProcessExecutionError that indicated swap creation failure; this meant
that the fallback logic could never be triggered.

This commit adds the required re-raise (as well as removing a duplicated
log message).

LP: #1897099

468aede... by Dan Watkins

.travis.yml: add integration-tests to Travis matrix (#600)

This is implemented as a copy/paste of the `citest` integration testing
script: the two are not intended to co-exist long-term, so it isn't
worth further complicating an already complex part of our Travis
configuration for short-term code reuse.

The two changes from the `citest` definition: the test framework
executed on the last line of `script`, and it is given a `name` so we
can easily ignore failures.

b0e7381... by Eduardo Otubo

ssh_util: handle non-default AuthorizedKeysFile config (#586)

The following commit merged all ssh keys into a default user file
`~/.ssh/authorized_keys` in sshd_config had multiple files configured for
AuthorizedKeysFile:

commit f1094b1a539044c0193165a41501480de0f8df14
Author: Eduardo Otubo <email address hidden>
Date: Thu Dec 5 17:37:35 2019 +0100

    Multiple file fix for AuthorizedKeysFile config (#60)

This commit ignored the case when sshd_config would have a single file for
AuthorizedKeysFile, but a non default configuration, for example
`~/.ssh/authorized_keys_foobar`. In this case cloud-init would grab all keys
from this file and write a new one, the default `~/.ssh/authorized_keys`
causing the bug.

rhbz: #1862967

Signed-off-by: Eduardo Otubo <email address hidden>

5a7f681... by Paride Legovini

bddeb: new --packaging-branch argument to pull packaging from branch (#576)

bddeb builds a .deb package using the template packaging files in
packages/debian/.

The new --packaging-branch flag allows to specify a git branch
where to pull the packaging (i.e. the debian/ directory) from.
This is useful to build a .deb package from master with the very
same packaging which is used for the uploads.

b94962b... by Lucas Albuquerque Medeiros de Moura

Add more integration tests (#615)

Translate the following tests from `cloud_tests` to the new integration test framework:

* test_runcmd.py
* seed_random_data.py
* set_hostname.py
* set_hostname_fqdn.py
* snap.py
* ssh_auth_key_fingerprints_disable.py
* ssh_auth_key_fingerprints_enable.py
* ssh_import_id.py
* ssh_keys_generate.py
* ssh_keys_provided.py
* timezone.py
* write_files.py

8766784... by Johnson Shi

DataSourceAzure: write marker file after report ready in preprovisioning (#590)

DataSourceAzure previously writes the preprovisioning
reported ready marker file before it goes through the
report ready workflow. On certain VM instances, the
marker file is successfully written but then reporting
ready fails.

Upon rare VM reboots by the platform, cloud-init sees
that the report ready marker file already exists.
The existence of this marker file tells cloud-init
not to report ready again (because it mistakenly
assumes that it already reported ready in
preprovisioning).

In this scenario, cloud-init instead erroneously
takes the reprovisioning workflow instead of
reporting ready again.