<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests/cloud_tests/testcases/modules, branch crux</title>
<subtitle> (mirror of https://github.com/vyos/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=crux'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2018-10-07T19:31:50+00:00</updated>
<entry>
<title>tests: fix apt_configure_primary to be more flexible</title>
<updated>2018-10-07T19:31:50+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-10-07T19:31:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=638f09e82260ea3256c387cd55408e0411f36c23'/>
<id>urn:sha1:638f09e82260ea3256c387cd55408e0411f36c23</id>
<content type='text'>
Commit d3e803ad316e6796e5d83e7e8f8f4f7224b92df9 added deb-src comments to
the cloud-init apt templates. This doubled the number of matching entries
seen in /etc/apt/sources.list in apt_configure_primary integration test.

This test was really asserting that GaTech urls were present in
/etc//apt/sources.list instead of archive.ubuntu.com. Fix the test to be a
bit more flexible in case cloud-init changes its bas apt template again.
</content>
</entry>
<entry>
<title>tests: allow skipping an entire cloud_test without running.</title>
<updated>2018-10-01T18:23:34+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-10-01T18:23:34+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=40768bad4c7eb966b2a8c1308cdae22e578b2413'/>
<id>urn:sha1:40768bad4c7eb966b2a8c1308cdae22e578b2413</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>tests: disable lxd tests on cosmic</title>
<updated>2018-09-28T20:47:28+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-28T20:47:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c239eb82f1bfe1d0c4b79f2a733f04cfb3277fbf'/>
<id>urn:sha1:c239eb82f1bfe1d0c4b79f2a733f04cfb3277fbf</id>
<content type='text'>
Skip lxd tests on cosmic for two reasons:
a.) bug 1795036 - 'lxd init' fails on cosmic kernel.
b.) apt install lxd installs via snap which can be slow
    as that will download core snap and lxd.
</content>
</entry>
<entry>
<title>cii-tests: use unittest2.SkipTest in ntp_chrony due to new deps</title>
<updated>2018-09-27T21:02:28+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-09-27T21:02:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=fb5015fe3f5078149463838b7974523646f94eab'/>
<id>urn:sha1:fb5015fe3f5078149463838b7974523646f94eab</id>
<content type='text'>
Git commitish fc4b966ba928b30b1c586407e752e0b51b1031e8 changed integration
test dependencies from unittest to unittest2.  Use unittest2.SkipTest in
test_chrony to avoid causing tracebacks.
</content>
</entry>
<entry>
<title>lxd: adjust to snap installed lxd.</title>
<updated>2018-09-26T21:29:27+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-09-26T21:29:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=facb92c5b55f4d27ee971eaf49c580fbf92ac2c3'/>
<id>urn:sha1:facb92c5b55f4d27ee971eaf49c580fbf92ac2c3</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>tests: disable other snap test as well</title>
<updated>2018-08-23T18:13:25+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2018-08-23T18:13:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=dab59087155d3963849a36b3f63ee662047f708b'/>
<id>urn:sha1:dab59087155d3963849a36b3f63ee662047f708b</id>
<content type='text'>
The snap test requires access to a proxy and currently the integration
tests do not handle this scenario. I am disabling the test until I can
loop back around and fix this.
</content>
</entry>
<entry>
<title>tests: disable snap, fix write_files binary</title>
<updated>2018-08-20T18:29:26+00:00</updated>
<author>
<name>Joshua Powers</name>
<email>josh.powers@canonical.com</email>
</author>
<published>2018-08-20T18:29:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a03ed8bf77add3ed920137e4cc6986caa414d1da'/>
<id>urn:sha1:a03ed8bf77add3ed920137e4cc6986caa414d1da</id>
<content type='text'>
The snap test requires access to a proxy and currently the integration
tests do not handle this scenario. I am disabling the test untill I can
loop back around and fix this.

The write_files test, specifically, the binary test is failing on cosmic
because the "binary" file we were writting was not a complete elf
executable, but we expected 'file' to identify it as such.

The change here is to simply use some 24 bytes of random, non-utf data
and check that file was written correctly via expected checksum.
</content>
</entry>
<entry>
<title>tests: drop salt-minion integration test</title>
<updated>2018-06-28T21:22:33+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-06-28T21:22:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5858136215753cffc2080c85429a3c7a3754741c'/>
<id>urn:sha1:5858136215753cffc2080c85429a3c7a3754741c</id>
<content type='text'>
The salt minion integration test as we had it did not do a whole lot
more than the unit tests on that module did.  Additionally, it caused
some transient failures at least in Ubuntu 18.04.

At a future date we may choose to add an integration test that installs
salt-minion and salt server and configures it to be a better test.

LP: #1778737
</content>
</entry>
<entry>
<title>tests: fix salt_minion integration test on bionic and later</title>
<updated>2018-06-12T22:42:54+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-06-12T22:42:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=27283c31f4bf85f40588cfa3b31389d70ec00243'/>
<id>urn:sha1:27283c31f4bf85f40588cfa3b31389d70ec00243</id>
<content type='text'>
In ubuntu, the salt-minion package version 2017.7.4+dfsg1-1 or later
automatically moves any seed keys from /etc/salt/pki/minion/ to
/var/lib/salt/pki/minion/. Fix integration tests to collect
either files in either /etc/salt/pki/minion/ or
/var/lib/salt/pki/minion/.
</content>
</entry>
<entry>
<title>tests: skip chrony integration tests on lxd running artful or older</title>
<updated>2018-06-12T17:54:30+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2018-06-12T17:54:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5ffcb511db8783aa9d32895f7017a7278d546f2f'/>
<id>urn:sha1:5ffcb511db8783aa9d32895f7017a7278d546f2f</id>
<content type='text'>
A fix for chrony support per LP: #1589780 is not expected in Artful or
older series. Skip the chrony suite of tests when running on a container
and ubuntu series represented is &lt;= artful as errors are expected.
</content>
</entry>
</feed>
