vyos-cloud-init.git/tests/unittests/test_handler, branch crux

write_files: add support for appending to files.

2018-12-06T18:26:32+00:00

Add 'append: true' to write_files entries to append 'content' to file specified by 'path' key. This modifies the file open mode to append.

tests: fix incorrect order of mocks in test_handle_zfs_root.

2018-11-28T18:23:33+00:00

The order of parameters to test_handle_zfs_root did not match the order of the mocks applied. Thanks to Jason Zions for pointing this out.

resizefs: Prefix discovered devpath with '/dev/' when path does not exist

2018-11-14T22:02:18+00:00

In some environments, like FreeBSD, gpart can return the device basename instead of the full path. If this discovered devpath does not exist and is missing the '/dev/' prefix, add that prefix in an attempt to find the device.

lxd: adjust to snap installed lxd.

2018-09-26T21:29:27+00:00

Relax expectation on path to lxc and lxd. The deb path still does install them in /usr/bin/ but that is overly pedantic. Add a 'lxd waitready' (present since lxd 0.5) to wait until lxd is ready before operating on it.

tests: Add mock for util.get_hostname.

2018-09-17T11:37:27+00:00

At present the host network settings bleed into the test environment causing the test test_handler_apt_source_v3 to fail if the host has a domain setting other then localdomain. LP: #1792799

user-data: jinja template to render instance-data.json in cloud-config

2018-09-11T17:31:46+00:00

Allow users to provide '## template: jinja' as the first line or their #cloud-config or custom script user-data parts. When this header exists, the cloud-config or script will be rendered as a jinja template. All instance metadata keys and values present in /run/cloud-init/instance-data.json will be available as jinja variables for the template. This means any cloud-config module or script can reference any standardized instance data in templates and scripts. Additionally, any standardized instance-data.json keys scoped below a '' key will be promoted as a top-level key for ease of reference in templates. This means that '{{ local_hostname }}' is the same as using the latest '{{ v#.local_hostname }}'. Since instance-data is written to /run/cloud-init/instance-data.json, make sure it is persisted across reboots when the cached datasource opject is reloaded. LP: #1791781

tests: Disallow use of util.subp except for where needed.

2018-09-05T16:02:25+00:00

In many cases, cloud-init uses 'util.subp' to run a subprocess. This is not really desirable in our unit tests as it makes the tests dependent upon existance of those utilities. The change here is to modify the base test case class (CiTestCase) to raise exception any time subp is called. Then, fix all callers. For cases where subp is necessary or actually desired, we can use it via a.) context hander CiTestCase.allow_subp(value) b.) class level self.allowed_subp = value Both cases the value is a list of acceptable executable names that will be called (essentially argv[0]). Some cleanups in AltCloud were done as the code was being updated.

lxd: Delete default network and detach device if lxd-init created them.

2018-06-16T02:00:15+00:00

Newer versions (3.0.1+) of lxd create the 'lxdbr0' network when 'lxd init --auto' is invoked. When cloud-init is given a network configuration to pass on to lxc and that config had no name specified or 'lxdbr0', then cloud-init would fail to create the network as it already exists. Similarly, we need to remove the device from the default profile so that the attach code can work. Also, add a _lxc method and use it to make sure we're getting the --force-local flag everywhere. LP: #1776958

tests: Avoid using https in httpretty, improve HttPretty test case.

2018-05-23T20:04:42+00:00

On OpenSuSE 42.3, we would get errors running tests/unittests/test_handler/test_handler_chef.py - test_myhttps_nonet raises a UnmockedError No mocking was registered, and real connections are not allowed - test_myhttps_net raises SSLError ("bad handshake: SysCallError(32, 'EPIPE')",) This fixes the errors by just using http instead of https. Also it modifies the HttprettyTestCase to do the httpretty activate and deactivate itself in setUp and tearDown. Then we don't have to decorate individual test_ methods. Also, we set httpretty.HTTPretty.allow_net_connect = False Test cases here should not reach out to a network resource. LP: #1771659

yaml_load/schema: Add invalid line and column nums to error message

2018-05-23T19:56:16+00:00

Yaml tracebacks are generally hard to read for average users. Add a bit of logic to util.yaml_load and schema validation to look for YAMLError.context_marker or problem_marker line and column counts. No longer log the full exceeption traceback from the yaml_load error, instead just LOG.warning for the specific error and point to the offending line and column where the problem exists.