<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests, branch 20.4</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=20.4</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=20.4'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2020-11-23T21:52:19+00:00</updated>
<entry>
<title>Ensure proper root permissions in integration tests (#664)</title>
<updated>2020-11-23T21:52:19+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2020-11-23T21:52:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=6e86d2a5649b3a9113923c73154ebf02224732a6'/>
<id>urn:sha1:6e86d2a5649b3a9113923c73154ebf02224732a6</id>
<content type='text'>
Tests previously assumed that when executing commands and transferring
files that user will have root permissions. This change updated
integration testing infrastructure so that is true.</content>
</entry>
<entry>
<title>LXD VM support in integration tests (#678)</title>
<updated>2020-11-23T18:12:52+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2020-11-23T18:12:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=8a493bf08d8b09d4f3a35dae725756d157844201'/>
<id>urn:sha1:8a493bf08d8b09d4f3a35dae725756d157844201</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Integration test for fallocate falling back to dd (#681)</title>
<updated>2020-11-23T17:50:57+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2020-11-23T17:50:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=e454dea5855019a5acdd6acafdef2ae07d069235'/>
<id>urn:sha1:e454dea5855019a5acdd6acafdef2ae07d069235</id>
<content type='text'>
See #585</content>
</entry>
<entry>
<title>Ability to hot-attach NICs to preprovisioned VMs before reprovisioning (#613)</title>
<updated>2020-11-23T15:04:05+00:00</updated>
<author>
<name>aswinrajamannar</name>
<email>39812128+aswinrajamannar@users.noreply.github.com</email>
</author>
<published>2020-11-23T15:04:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a4d0feb050e32277a218e45bfb6a496d26ff46d0'/>
<id>urn:sha1:a4d0feb050e32277a218e45bfb6a496d26ff46d0</id>
<content type='text'>
Adds the ability to run the Azure preprovisioned VMs as NIC-less and
then hot-attach them when assigned for reprovision.

The NIC on the preprovisioned VM is hot-detached as soon as it reports
ready and goes into wait for one or more interfaces to be hot-attached.
Once they are attached, cloud-init gets the expected number of NICs (in
case there are more than one) that will be attached from IMDS and waits
until all of them are attached. After all the NICs are attached,
reprovision proceeds as usual.</content>
</entry>
<entry>
<title>Support configuring SSH host certificates. (#660)</title>
<updated>2020-11-20T20:59:51+00:00</updated>
<author>
<name>Jonathan Lung</name>
<email>lungj@users.noreply.github.com</email>
</author>
<published>2020-11-20T20:59:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=66b4be8b6da188a0667bd8c86a25155b6f4f3f6c'/>
<id>urn:sha1:66b4be8b6da188a0667bd8c86a25155b6f4f3f6c</id>
<content type='text'>
Existing config writes keys to /etc/ssh after deleting files matching
a glob that includes certificate files. Since sshd looks for
certificates in the same directory as the keys, a host certificate
must be placed in this directory. This update enables the certificate's
contents to be specified along with the keys.

Co-authored-by: jonathan lung &lt;lungj@heresjono.com&gt;
Co-authored-by: jonathan lung &lt;jlung@kepler.space&gt;</content>
</entry>
<entry>
<title>add integration test for LP: #1900837 (#679)</title>
<updated>2020-11-20T19:12:54+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-11-20T19:12:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5d4a9a4a50a496d27510f63217bcc0c25d9a8939'/>
<id>urn:sha1:5d4a9a4a50a496d27510f63217bcc0c25d9a8939</id>
<content type='text'>
As the first test of this SRU cycle, this also introduces the
sru_2020_11 mark to allow us to easily identify the set of tests
generated for this SRU.</content>
</entry>
<entry>
<title>cc_resizefs on FreeBSD: Fix _can_skip_ufs_resize (#655)</title>
<updated>2020-11-19T22:19:16+00:00</updated>
<author>
<name>Mina Galić</name>
<email>me+git@igalic.co</email>
</author>
<published>2020-11-19T22:19:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=12ef7541c2d0c6b2cd510f95fda53ca9c8333064'/>
<id>urn:sha1:12ef7541c2d0c6b2cd510f95fda53ca9c8333064</id>
<content type='text'>
On FreeBSD, if a UFS has trim: (-t) or MAC multilabel: (-l) flag, resize
FS fail, because the _can_skip_ufs_resize check gets tripped up by the
missing options.

This was reported at FreeBSD Bugzilla: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=250496 and as
LP: #1901958

Rather than fixing the parser as in the patches proposed there (and
attempted in #636) this pull-request rips out all of it, and simplifies
the code.  We now use `growfs -N` and check if that returns an error. If
it returns the correct kind of error, we can skip the resize, because we
either are at the correct size, or the filesystem in question is broken
or not UFS. If it returns the wrong kind of error, we just re-raise it.

LP: #1901958</content>
</entry>
<entry>
<title>DataSourceAzure: push dmesg log to KVP (#670)</title>
<updated>2020-11-19T18:38:27+00:00</updated>
<author>
<name>Anh Vo</name>
<email>anhvo@microsoft.com</email>
</author>
<published>2020-11-19T18:38:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=73e704e3690611625e3cda060a7a6a81492af9d2'/>
<id>urn:sha1:73e704e3690611625e3cda060a7a6a81492af9d2</id>
<content type='text'>
Pushing dmesg log to KVP to help troubleshoot VM boot issues</content>
</entry>
<entry>
<title>Make mount in place for tests work (#667)</title>
<updated>2020-11-19T17:54:35+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2020-11-19T17:54:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=9707a08a82161cd4129f6cdd10978cde50bea747'/>
<id>urn:sha1:9707a08a82161cd4129f6cdd10978cde50bea747</id>
<content type='text'>
IMAGE_SOURCE = 'IN_PLACE' wasn't working previously. Replaced
LXD launch with an init, then mount, then start.</content>
</entry>
<entry>
<title>integration_tests: restore emission of settings to log (#657)</title>
<updated>2020-11-19T17:42:49+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2020-11-19T17:42:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=bfaee8cc9b8fd23dbc118ae548fc2ca695a0d707'/>
<id>urn:sha1:bfaee8cc9b8fd23dbc118ae548fc2ca695a0d707</id>
<content type='text'>
</content>
</entry>
</feed>
