| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
| |
| |
| |
| |
| | |
`test_seed_random_data.py` was failing on openstack as openstack
provides additional binary seed data to the end of the specified file.
The test has been changed to only read the ascii porition of
seed file.
|
| | | |
|
| | |
| |
| |
| | |
New datasource utilizing UpCloud metadata API, including relevant unit
tests and documentation.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In LXD containers, the default interface is named eth0. In VMs, it
isn't; it's renamed by systemd (likely to enp5s0, but we can't rely on
that). This means that, on VMs, the network configuration we specify
for "eth0" doesn't match an interface in the system and so is not
applied.
This modifies the test to set a MAC address in a match clause in the
network configuration and on the eth0 interface (which is the LXD name
in both containers and VMs pre-rename): this ensures that the specified
configuration applies in both cases.
|
| | |
| |
| |
| |
| |
| |
| | |
Add support for openstack's dynamic vendor data, which appears under openstack/latest/vendor_data2.json
This adds vendor_data2 to all pathways; it should be a no-op for non-OpenStack providers.
LP: #1841104
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Since version 1.9.1, @includedir can be used in the sudoers files
instead of #includedir:
https://github.com/sudo-project/sudo/releases/tag/SUDO_1_9_1
Actually "@includedir" is the modern syntax, and "#includedir" the historic
syntax. It has been considered that "#includedir" was too puzzling because
it started with a "#" that otherwise denotes comments.
This happens to be the default in SUSE Linux enterprise sudoer package,
so cloudinit should take this into account.
Otherwise, cloudinit was adding an extra #includedir, which was
resulting on the files under /etc/sudoers.d being included twice, one by
@includedir from the SUSE package, one by the @includedir from
cloudinit. The consequence of this, was that if you were defining an
Cmnd_Alias inside any of those files, this was being defined twice and
creating an error when using sudo.
|
| | |\
| | |
| | |
| | |
| | | |
upstream/20.4.1 was used to release the 20.4.1 hotfix. Merging it into
master reconciles that fork in history, and integrates both the 20.4.1
changelog and tag into our main history.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If cloud-init is enabled on VMware platform, cloud-init will wait until
its configuration file is ready and currently the max wait is 90
seconds by default. With our test, this configuration file should be
ready within 1 second, so change it to 15 seconds for better
performance. Also update the documentation about how to change the
default value in cloud-init configuration file.
|
| | | | |
|
| | | |
| | |
| | | |
Signed-off-by: Jordi Massaguer Pla <jmassaguerpla@suse.de>
|
| | | | |
|
| | | |
| | |
| | |
| | | |
We've had some first time contributors still end up trying to submit via
Launchpad: this commit underlines that this is not necessary.
|
| | | |
| | |
| | |
| | |
| | | |
The tox pylint command was failing because of competing dependencies in
the multiple requirements files. Given that we plan on no longer
updating cloud_tests, we also no longer need to lint them.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
pycloudlib no longer raises exceptions when cloud-init fails to start,
and the API has been updated accordingly. Changes have been made to
integration tests accordingly
|
| | | |
| | |
| | |
| | | |
Stop requiring compartment_id for OCI and project_id for GCE since they
can now be inferred in pycloudlib.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Two shell code blocks are not marked as such, confusing rst to consider
them as yaml. Be explicit about their syntax, and use $ prompt to match
elsewhere in the docs.
/home/travis/build/canonical/cloud-init/doc/rtd/topics/format.rst:28: WARNING: Could not lex literal_block as "yaml". Highlighting skipped.
/home/travis/build/canonical/cloud-init/doc/rtd/topics/format.rst:52: WARNING: Could not lex literal_block as "yaml". Highlighting skipped.
Signed-off-by: Dan Kenigsberg <danken@redhat.com>
|
| | | |
| | |
| | |
| | |
| | | |
The company name has two distinct words.
Signed-off-by: Dan Kenigsberg <danken@redhat.com>
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Ubuntu cloud images ship /etc/cloud/build.info which includes a line
with the build serial used to identify the image:
serial: 20210108
This is valuable information when verifying Ubuntu issues (to confirm
that testing is happening against the expected image), but is also
useful when debugging test failures: manifests of all packages in (the
base) images can be found at http://cloud-images.ubuntu.com/
|
| | | |
| | |
| | | |
This reverts commit b0e73814db4027dba0b7dc0282e295b7f653325c.
|
| | | |
| | |
| | | |
This feature will modify VMware datasource to read from meta data and user data which are specified by VMware vSphere user. If meta data/user data are found in cloud-init configuration directory, datasource will parse the meta data/network and user data from the configuration file, otherwise it will continue to parse them from traditional customization configuration file as before. The supported meta data file is in json or yaml format.
|
| | | |
| | |
| | |
| | | |
Route '-net' parameter is incompatible with /32 IPv4 addresses so we
have to use '-host' in that case.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We have replicated their functionality in the new integration testing
framework, and have seen that running for long enough to be confident in
relying on it.
cloud_tests are still used in cloud-init's nightly test runs: this is
only modifying what we run in Travis.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The documentation did not mention that the given data may not be the
exact string written: the cloud's random data may be added to it.
Additionally, the documentation of the command key was incorrect.
test_seed_random_data was updated to check that the given data is a
prefix of the written data, to match cloud-init's expected (and, now,
documented) behaviour.
LP: #1911227
|
| | | |
| | |
| | | |
LP: #1911230
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
pacman uses `-u` instead of `upgrade` to trigger a system upgrade, fix
the command handling so this is properly accounted for. as is, the
resulting command attempts to install a (non-existent) `upgrade` package
Co-authored-by: Rick Harding <rharding@mitechie.com>
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With the changes for SSH public keys to be retrieved from IMDS as a
first option, when a key is passed through not in the raw SSH public key
format it causes an issue and the key is not added to the user's
authorized_keys file.
This PR will temporarily disable this behavior until a permanent fix is
put in place.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
IPV6_AUTOCONF needs to be set to 'no' on RHEL so NetworkManager can
properly acquire ipv6 address.
rhbz: #1859695
Signed-off-by: Eduardo Otubo <otubo@redhat.com>
|
| | | |
| | |
| | |
| | |
| | | |
Added some missing IPv6 subnet configuration types
(ipv6_dhcpv6-stateful, ipv6_dhcpv6-stateless, ipv6_slaac) to Networking
config v1 documentation.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This introduces PUBLIC_SSH_KEY, to configure what public SSH key should
be used to access systems under test, and KEYPAIR_NAME, to configure the
name used in clouds for that SSH key (or the default SSH key, in
PUBLIC_SSH_KEY's absence).
|
| | | |
| | |
| | |
| | | |
1. fix a typo in cloud-init.1
2. add xiachen-rh as contributor
|
| | | |
| | |
| | |
| | |
| | | |
We don't currently document our passthrough behaviour, which has lead to
some user confusion about what they can rely upon on Ubuntu systems.
This clarifies our support.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This reverts commits fad919aa2c894abaa3af88aed1e064c1220937fe ("stale:
disable check for holiday break (#735)") and
e4f2d6139a802e659c571f581763eddeee715e2f ("stale: fix error in
definition (#740)").
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Our HACKING doc is very long, making it hard to justify expanding or
restructuring its content too much. This moves the testing section to
its own doc, and adds section headers in to make finding/linking to
testing guidelines easier.
To avoid confusion, the title of debugging.rst is changed.
|
| | | | |
|
| | | |
| | |
| | |
| | | |
This should fix the error, and also allows us to manually trigger the
workflow.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This gives us more detailed integration testing output by default.
This will make debugging failures reported by users/developers easier to
debug, as it removes the need for an initial round-trip to get the
output we need for debugging. It will also make debugging intermittent
failures easier: there will definitely be log output from runs which
exhibit the intermittent failure.
|
| | | |
| | |
| | |
| | |
| | | |
This makes it easier to copy/paste commit messages prepared elsewhere
into the GitHub UI (and also means that the formatting in the GH UI more
closely matches how the commit message will be consumed elsewhere).
|
| | | |
| | |
| | |
| | | |
We're unlikely to see any activity on many PRs over the next couple of
weeks, so don't close out inactive PRs for the duration.
|
| | | |
| | |
| | |
| | | |
This makes it easier to find the failure logs when you're running a
bunch of similar tests in parallel.
|
