(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2021-12-16T02:16:38+00:00 2021-12-16T02:16:38+00:00 James Falcon james.falcon@canonical.com 2021-12-16T02:16:38+00:00 urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf Applied Black and isort, fixed any linting issues, updated tox.ini and CI. 2021-02-22T17:03:53+00:00 Daniel Watkins oddbloke@ubuntu.com 2021-02-22T17:03:53+00:00 urn:sha1:38aee6eebb160d46287c63a979bb897b15bb2f96 pycloudlib has modified the way LXD executes tests (https://github.com/canonical/pycloudlib/pull/114): it will always use SSH to access them by default, instead of using `lxc exec`. This behaviour is transparent for them majority of cloud-init's integration tests, but some currently depend on using `lxc exec` to access instances with (intentionally) broken networking: obviously these are not accessible via SSH. pycloudlib retains support for switching an instance to use `lxc exec`. This commit introduces the `lxd_use_exec` mark, which tests can use to indicate to the integration testing framework that they should be so switched, and applies it to all applicable tests. 2021-02-18T16:17:26+00:00 Daniel Watkins oddbloke@ubuntu.com 2021-02-18T16:17:26+00:00 urn:sha1:5a9008e53d7cf987b5cfb78964d2bd987d180993 Using the same MAC address results in strange test behaviour if more than one such instance is up: traffic gets routed to an arbitrary interface with the given MAC address. This can happen if running tests in parallel, or on a system which retains test instances from previous runs. The introduction of tests/integration_tests/__init__.py means that pylint now checks the integration tests: this commit also addresses those failures. 2021-02-05T22:11:14+00:00 Daniel Watkins oddbloke@ubuntu.com 2021-02-05T22:11:14+00:00 urn:sha1:3a0a5894d112d667f313d7fb3ab0850a39bc3020 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. 2021-01-13T22:19:17+00:00 Pavel Abalikhin anpavl@gmail.com 2021-01-13T22:19:17+00:00 urn:sha1:9a258eebd96aa5ad4486dba1fe86bea5bcf00c2f Route '-net' parameter is incompatible with /32 IPv4 addresses so we have to use '-host' in that case.