<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests/unittests/test_handler, branch 20.4</title>
<subtitle> (mirror of https://github.com/marekm72/vyos-cloud-init.git)
</subtitle>
<id>https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.4</id>
<link rel='self' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=20.4'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/'/>
<updated>2020-11-19T22:19:16+00:00</updated>
<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/marekm72/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>cli: add --system param to allow validating system user-data on a machine (#575)</title>
<updated>2020-11-18T14:23:44+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2020-11-18T14:23:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=f680114446a5a20ce88f3d10d966811a774c8e8f'/>
<id>urn:sha1:f680114446a5a20ce88f3d10d966811a774c8e8f</id>
<content type='text'>
Allow root user to validate the userdata provided to the launched
machine using `cloud-init devel schema --system`</content>
</entry>
<entry>
<title>Add config modules for controlling IBM PowerVM RMC. (#584)</title>
<updated>2020-10-28T18:06:09+00:00</updated>
<author>
<name>Aman306</name>
<email>45781773+Aman306@users.noreply.github.com</email>
</author>
<published>2020-10-28T18:06:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=f99d4f96b00a9cfec1c721d364cbfd728674e5dc'/>
<id>urn:sha1:f99d4f96b00a9cfec1c721d364cbfd728674e5dc</id>
<content type='text'>
Reliable Scalable Cluster Technology (RSCT) is a set of software
components that together provide a comprehensive clustering
environment(RAS features) for IBM PowerVM based virtual machines. RSCT
includes the Resource Monitoring and Control (RMC) subsystem. RMC is a
generalized framework used for managing, monitoring, and manipulating
resources. RMC runs as a daemon process on individual machines and needs
creation of unique node id and restarts during VM boot.

LP: #1895979

Co-authored-by: Scott Moser &lt;smoser@brickies.net&gt;</content>
</entry>
<entry>
<title>create a shutdown_command method in distro classes (#567)</title>
<updated>2020-09-15T19:51:52+00:00</updated>
<author>
<name>Emmanuel Thomé</name>
<email>Emmanuel.Thome@inria.fr</email>
</author>
<published>2020-09-15T19:51:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=6d332e5c8dbfb6521a530b1fa49d73da51efff96'/>
<id>urn:sha1:6d332e5c8dbfb6521a530b1fa49d73da51efff96</id>
<content type='text'>
Under FreeBSD, we want to use "shutdown -p" for poweroff.

Alpine Linux also has some specificities.

We choose to define a method that returns the shutdown command line to
use, rather than a method that actually does the shutdown. This makes it
easier to have the tests in test_handler_power_state do their
verifications.

Two tests are added for the special behaviours that are known so far.</content>
</entry>
<entry>
<title>LXD: detach network from profile before deleting it (#542)</title>
<updated>2020-08-27T15:20:35+00:00</updated>
<author>
<name>Paride Legovini</name>
<email>paride.legovini@canonical.com</email>
</author>
<published>2020-08-27T15:20:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=1f3a225af78dbfbff75c3faad28a5dc8cad0d1e3'/>
<id>urn:sha1:1f3a225af78dbfbff75c3faad28a5dc8cad0d1e3</id>
<content type='text'>
* LXD: detach network from profile before deleting it

When cleaning up the bridge network created by default by LXD as part
of the `lxd init` process detach the network its profile before deleting
it. LXD will otherwise refuse to delete it with error:

  Error: The network is currently in use.

Discussion with LXD upstream: https://github.com/lxc/lxd/issues/7804.

LP: #1776958

* LXD bridge deletion: fail if bridge exists but can't be deleted

* LXD bridge deletion: remove useless failure logging</content>
</entry>
<entry>
<title>Add Alpine Linux support. (#535)</title>
<updated>2020-08-19T23:18:25+00:00</updated>
<author>
<name>dermotbradley</name>
<email>dermot_bradley@yahoo.com</email>
</author>
<published>2020-08-19T23:18:25+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=79a8ce7e714ae1686c10bff77612eab0f6eccc95'/>
<id>urn:sha1:79a8ce7e714ae1686c10bff77612eab0f6eccc95</id>
<content type='text'>
Add new module cc_apk_configure for creating Alpine /etc/apk/repositories file.
Modify cc_ca_certs, cc_ntp, cc_power_state_change, and cc_resolv_conf for Alpine.
Add Alpine template files for Chrony and Busybox NTP support.
Add Alpine template file for /etc/hosts.

</content>
</entry>
<entry>
<title>Detect kernel version before swap file creation (#428)</title>
<updated>2020-08-18T21:12:02+00:00</updated>
<author>
<name>Eduardo Otubo</name>
<email>otubo@redhat.com</email>
</author>
<published>2020-08-18T21:12:02+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=b749548a9eb43b34cce64f8688107645411abc8c'/>
<id>urn:sha1:b749548a9eb43b34cce64f8688107645411abc8c</id>
<content type='text'>
According to man page `man 8 swapon', "Preallocated swap files are
supported on XFS since Linux 4.18". This patch checks for kernel version
before attepting to create swapfile, using dd for XFS only on kernel
versions &lt;= 4.18 or btrfs.

Add new func util.kernel_version which returns a tuple of ints (major, minor)

Signed-off-by: Eduardo Otubo otubo@redhat.com</content>
</entry>
<entry>
<title>cc_ca_certs.py: fix blank line problem when removing CAs and adding new one (#483)</title>
<updated>2020-07-15T20:24:43+00:00</updated>
<author>
<name>dermotbradley</name>
<email>dermot_bradley@yahoo.com</email>
</author>
<published>2020-07-15T20:24:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=c0d239c7eadeae9c9e0b4e692b49e79c8ffcafd2'/>
<id>urn:sha1:c0d239c7eadeae9c9e0b4e692b49e79c8ffcafd2</id>
<content type='text'>
Problem: When cc_ca_certs configuration has both "remove-defaults: true"
and also specifies one, or more, new trusted CAs to add then the resultant
/etc/ca-certificates.conf file's 1st line is blank. As noted in comments
in the existing cc_ca_certs.py code blank lines in this file cause problems.

Fix: Before adding the cloud-init CA filename to this file first check the
size of the file - if is is empty (as all existing CAs have been deleted)
then write only the cloud-init CA filename to the file rather than appending
it to the file.</content>
</entry>
<entry>
<title>cc_mounts: handle missing fstab (#484)</title>
<updated>2020-07-10T13:08:44+00:00</updated>
<author>
<name>Ryan Harper</name>
<email>ryan.harper@canonical.com</email>
</author>
<published>2020-07-10T13:08:44+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=3d06abc2e0017436dadbf9c26fefa9f95368db9a'/>
<id>urn:sha1:3d06abc2e0017436dadbf9c26fefa9f95368db9a</id>
<content type='text'>
Do not fail if /etc/fstab is not present.  Some images, like container
rootfs may not include this file by default.

LP: #1886531</content>
</entry>
<entry>
<title>Disable ec2 mirror for non aws instances (#390)</title>
<updated>2020-06-30T22:25:26+00:00</updated>
<author>
<name>lucasmoura</name>
<email>lucas.moura@canonical.com</email>
</author>
<published>2020-06-30T22:25:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/marekm72/vyos-cloud-init.git/commit/?id=3fcdacc8995d6908858aceaf1da7ee5ff090fc04'/>
<id>urn:sha1:3fcdacc8995d6908858aceaf1da7ee5ff090fc04</id>
<content type='text'>
For versions before 20.2, we allowed the use of ec2 mirrors if the datasource availability_zone matches one of the ec2 regions. We are now updating that behavior to allow allow the use of ec2 mirrors on ec2 instances or if the user directly passes an an ec2 mirror url through #cloud-config apt directives.

LP: #1456277</content>
</entry>
</feed>
