vyos-cloud-init.git/tests/integration_tests, branch mergify/bp/circinus/pr-85

tests: when generating crypted password, generate in target env (#1252)

2022-02-14T15:51:03+00:00

There are inconsistencies for cryptographic libraries across major distribution releases. From a bionic host, which doesn't support yescrypt hashing scheme, attempting run run crypt.crypt locally using a yescrypt hash from a Jammmy /etc/shadow file will result in failure to produce an encrypted password. For "unsupported" hash schemes, crypt.crypt returns None. To avoid inconsistencies of python cryptographic libs across Linux releases, perform the password encryption on the system under test.

test_apt_security: azure platform has specific security URL overrides (#1263)

2022-02-11T14:34:43+00:00

Delivered in /etc/cloud/cloud.cfg.d/90-azure.cfg

tests: lsblk --json output changes mountpoint key to mountpoinst [] (#1261)

2022-02-10T22:37:17+00:00

Ubuntu Jammy output from lsblk --json now contains 'mountpoints': [...] instead of 'mountpoint' for children devs. Let our integration test handle either case.

mounts: fix mount opts string for ephemeral disk (#1250)

2022-02-10T22:09:03+00:00

Fixes the spaces introduced in #1213 Signed-off-by: Chris Patterson

Shell script handlers by freq (#1166)

2022-02-10T21:49:38+00:00

Handlers for per-boot/per-instance/per-once multipart MIME Add handlers for adding scripts to userdata that can be run at various frequencies. Scripts of type x-shellscript-per-boot, x-shellscript-per-instance, or x-shellscript-per-once can be added to a multipart MIME userdata message as part of instance userdata. These scripts will then be added to the appropriate per-boot, per-instance, or per-once directory in /var/lib/cloud/scripts/ during processing of userdata.

cloud-id: publish /run/cloud-init/cloud-id- files (#1244)

2022-02-10T20:18:00+00:00

Once a valid datasource is detected, publish the following artifacts to expedite cloud-identification without having to invoke cloud-id from shell scripts or sheling out from python. These files can also be relied on in systemd ConditionPathExists directives to limit execution of services and units to specific clouds. /run/cloud-init/cloud-id: - A symlink with content that is the canonical cloud-id of the datasource detected. This content is the same lower-case value as the output of /usr/bin/cloud-id. /run/cloud-init/cloud-id-: - A single file which will contain the canonical cloud-id encoded in the filename

tests: do not check instance.pull_file().ok() (#1246)

2022-02-07T14:46:16+00:00

Test pycloudlib's BaseInstance.pull_file doesn't return a Result object. So we can't call ok() on the response in integration tests. Leave the try/except handling as pull_file will raise an IOError if there is an error connecting via paramiko's sftp.get.

testing: stop universally overwriting /etc/cloud/cloud.cfg.d (#1237)

2022-02-03T22:05:02+00:00

As part of IN_PLACE testing, /etc/cloud/cloud.cfg.d get overwritten by what's in the source tree. This can cause problems when the directory is mounted in, because tests need the ability to modify files in /etc/cloud. Attempting to 'lxc file push' instead will fail on LXD VMs because the LXD agent isn't available yet. If such functionality is desired, one can temporarily use the 'lxd_setup' mark while writing a test and push the files manually.

Integration test changes (#1240)

2022-02-03T21:37:14+00:00

* Wrap the log fetching code in a try/except in case file is missing * Stop checking NoCloud seed dir when testing datasource detection

integration: do not LXD bind mount /etc/cloud/cloud.cfg.d (#1234)

2022-02-03T04:38:56+00:00

Since lxc bind mounts will be read-only as nobody:nogroup we don't want to bind mount /etc/cloud/cloud.cfg.d into the instance because some tests add artifacts to /etc/cloud/cloud.cfg.d. Also make LXD push_file pull_file methods assert that the file transfer was a success, otherwise we miss the root-cause for test failures. This resulted in failed Jenkins runs in test_lxd_discovery with a symptom of NoCloud being detected instead of LXD datasource. The root-case was that instance.file_push failed due to permission errors for root on the bind mounted /etc/cloud/cloud.cfg.d. Also bump pycloudlib commitish to get Azure Jammy image support.