(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=22.1 2021-09-29T23:32:53+00:00 2021-09-29T23:32:53+00:00 James Falcon james.falcon@canonical.com 2021-09-29T23:32:53+00:00 urn:sha1:ba083245537abd5bf5942fbe851e21eb8f245000 Cloud tests have been replaced with integration tests 2020-04-24T13:26:51+00:00 Daniel Watkins oddbloke@ubuntu.com 2020-04-24T13:26:51+00:00 urn:sha1:38a7e6e9756fdab31264c0d6e93d20432ed111ac These libraries provide backports of Python 3's stdlib components to Python 2. As we only support Python 3, we can simply use the stdlib now. This pull request does the following: * removes some unneeded compatibility code for the old spelling of `assertRaisesRegex` * replaces invocations of the Python 2-only `assertItemsEqual` with its new name, `assertCountEqual` * replaces all usage of `unittest2` with `unittest` * replaces all usage of `contextlib2` with `contextlib` * drops `unittest2` and `contextlib2` from requirements files and tox.ini It also rewrites some `test_azure` helpers to use bare asserts. We were seeing a strange error in xenial builds of this branch which appear to be stemming from the AssertionError that pytest produces being _different_ from the standard AssertionError. This means that the modified helpers weren't behaving correctly, because they weren't catching AssertionErrors as one would expect. (I believe this is related, in some way, to https://github.com/pytest-dev/pytest/issues/645, but the only version of pytest where we're affected is so far in the past that it's not worth pursuing it any further as we have a workaround.) 2019-02-22T09:41:28+00:00 Chad Smith chad.smith@canonical.com 2019-02-22T09:41:28+00:00 urn:sha1:e7a8f81e6eee390ce6920df053bf7467b5e4dbd7 When integration tests verification fails, the object returned contains has 'error' and 'traceback' keys. Each key can contain empty strings. If the simplified 'error' message is empty, fallback and use the more verbose full 'traceback' text in the failure summary. 2018-10-01T18:23:34+00:00 Scott Moser smoser@ubuntu.com 2018-10-01T18:23:34+00:00 urn:sha1:40768bad4c7eb966b2a8c1308cdae22e578b2413 Individual skipTest or setUp SkipTest will still launch the instance. This allows us to stop the running of the instance so we don't waste cycles or boot systems that are known to fail. Also replace remaining unittest usage in tests/cloud_tests/ with unittest2. 2018-06-12T19:15:31+00:00 Chad Smith chad.smith@canonical.com 2018-06-12T19:15:31+00:00 urn:sha1:d0f6c4602f9cc412d372e10bd7411ff0214c1435 Integration tests will now provide a brief summary for test failures listed by platform and distribution. The failure summary will only consist of failed test name and assert error message. Drop the verbose dictionary of all integration test output because this content is unreadable given the large number of integration test results listed within this dictionary. 2018-03-16T19:43:31+00:00 Chad Smith chad.smith@canonical.com 2018-03-16T19:43:31+00:00 urn:sha1:a1f678f8ebc080d4737f32275f42947b84ae025a Support installing and configuring snaps on ubuntu systems. Now, cloud-config files can provide a list or dictionary of snap:assertions which will be allow configuration of snapd on a system via 'snap ack' calls. The snap:commands configuration option supports arbitrary system commands intended to interact with snappy's cli. This allows users to run arbitrary snappy commands to create users, download, install and configure snap packages and snapd. This branch also deprecates old snappy and snap_config modules leaving warnings in documentation and runtime for consumers of these modules. Deprecated snap* modules will be dropped in cloud-init v.18.2 release. 2018-01-25T19:26:34+00:00 Scott Moser smoser@ubuntu.com 2018-01-25T19:26:34+00:00 urn:sha1:bc84f5023f795c261e32cf0690b2d29e12cfaedd This adds collection a gzip compressed systemd journal on systemd systems. The file can later be reviewed with:   zcat system.journal.gz > system.journal   journalctl --file=system.journal [-o short-monotonic ..] To support this:   * modify test harness infrastructure to not assume content is utf-8.   * fix lxd platform to support make '_execute' return bytes rather     than a string. https://github.com/lxc/pylxd/issues/268 Also switched the base collectors to use /bin/sh as others already did. 2017-06-08T22:24:17+00:00 Wesley Wiedenmeier wesley.wiedenmeier@gmail.com 2017-06-08T22:23:31+00:00 urn:sha1:76d58265e34851b78e952a7f275340863c90a9f5 Massive update to clean up and greatly enhance the integration testing framework developed by Wesley Wiedenmeier. - Updated tox environment to run integration test 'citest' to utilize pylxd 2.2.3 - Add support for distro feature flags - add framework for feature flags to release config with feature groups and overrides allowed in any release conf override level - add support for feature flags in platform and config handling - during collect, skip testcases that require features not supported by the image with a warning message - Enable additional distros (i.e. centos, debian) - Add 'bddeb' command to build a deb from the current working tree cleanly in a container, so deps do not have to be installed on host - Adds a command line option '--preserve-data' that ensures that collected data will be left after tests run. This also allows the directory to store collected data in during the run command to be specified using '--data-dir'. - Updated Read the Docs testing page and doc strings for pep 257 compliance 2017-04-21T14:14:47+00:00 Joshua Powers josh.powers@canonical.com 2017-04-06T18:14:29+00:00 urn:sha1:5afe4cd0797a12d07ea19b9715b720d47bdea401 This will change all instances of LOG.warn to LOG.warning as warn is now a deprecated method. It will also make sure any logging uses lazy logging by passing string format arguments as function parameters. 2016-12-22T22:41:39+00:00 Wesley Wiedenmeier wesley.wiedenmeier@gmail.com 2016-12-22T22:27:37+00:00 urn:sha1:f53fc46aa732e3b29991b3e5e39da31a722945ee The adds in end-to-end testing of cloud-init. The framework utilizes LXD and cloud images as a backend to test user-data passed in. Arbitrary data is then captured from predefined commands specified by the user. After collection, data verification is completed by running a series of Python unit tests against the collected data. Currently only the Ubuntu Trusty, Xenial, Yakkety, and Zesty releases are supported. Test cases for 50% of the modules is complete and available. Additionally a Read the Docs file was created to guide test writing and execution.