<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/cloudinit/config/cc_lxd.py, branch rolling</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=rolling</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2021-12-16T02:16:38+00:00</updated>
<entry>
<title>Adopt Black and isort (SC-700) (#1157)</title>
<updated>2021-12-16T02:16:38+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2021-12-16T02:16:38+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf'/>
<id>urn:sha1:bae9b11da9ed7dd0b16fe5adeaf4774b7cc628cf</id>
<content type='text'>
Applied Black and isort, fixed any linting issues, updated tox.ini
and CI.
</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/vyos/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>Move subp into its own module. (#416)</title>
<updated>2020-06-08T16:49:12+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2020-06-08T16:49:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=3c551f6ebc12f7729a2755c89b19b9000e27cc88'/>
<id>urn:sha1:3c551f6ebc12f7729a2755c89b19b9000e27cc88</id>
<content type='text'>
This was painful, but it finishes a TODO from cloudinit/subp.py.

It moves the following from util to subp:
  ProcessExecutionError
  subp
  which
  target_path

I moved subp_blob_in_tempfile into cc_chef, which is its only caller.
That saved us from having to deal with it using write_file
and temp_utils from subp (which does not import any cloudinit things now).

It is arguable that 'target_path' could be moved to a 'path_utils' or
something, but in order to use it from subp and also from utils,
we had to get it out of utils.</content>
</entry>
<entry>
<title>replace any deprecated log.warn with log.warning</title>
<updated>2019-10-17T14:36:40+00:00</updated>
<author>
<name>Dominic Schlegel</name>
<email>dominic.schlegel@hostpoint.ch</email>
</author>
<published>2019-10-17T14:36:40+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=7e699256b319cdf41e747211763e593a6b5f3393'/>
<id>urn:sha1:7e699256b319cdf41e747211763e593a6b5f3393</id>
<content type='text'>
Commit 6797e822959b84c98cf73e02b2a6e3d6ab3fd4fe replaced
the LOG.warn calls that linters were warning about; this
also replaces calls that linters would not have recognised
(as `log` is generally a parameter in these scenarios).

LP: #1508442
</content>
</entry>
<entry>
<title>Fix a couple of issues raised by a coverity scan</title>
<updated>2019-07-10T23:17:12+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>daniel.watkins@canonical.com</email>
</author>
<published>2019-07-10T23:17:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=217c89369c3b16f11333f0090e059f76fc5d7937'/>
<id>urn:sha1:217c89369c3b16f11333f0090e059f76fc5d7937</id>
<content type='text'>
* cc_lxd: fix copy/paste error in debug logging
* DataSourceCloudSigma: remove unreachable code
  * This unreachable code was introduced in a refactor (in 2015) which
    removed the need for an exception handler, but retained the logging
    from the exception handler as an unreachable fall-through.
</content>
</entry>
<entry>
<title>lxd: install zfs-linux instead of zfs meta package</title>
<updated>2019-01-25T17:46:33+00:00</updated>
<author>
<name>Johnson Shi</name>
<email>johnson@johnsonshi.com</email>
</author>
<published>2019-01-25T17:46:33+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c283321bb118d5408390e12b173440f57bd2c160'/>
<id>urn:sha1:c283321bb118d5408390e12b173440f57bd2c160</id>
<content type='text'>
When using the LXD module cloud-init will attempt
to install ZFS if it does not exist on the target
system. However instead of installing the `zfsutils-linux`
package it attempts to install `zfs` resulting in an error.

Ubuntu Xenial (16.04) has zfs meta package, but Bionic (18.04)
does not. Use the specific base package instead of zfs meta.

Co-authored-by: Michael Skalka &lt;michael.skalka@canonical.com&gt;

LP: #1799779
</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>pylint: Fix pylint warnings reported in pylint 2.0.0.</title>
<updated>2018-07-21T15:30:58+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-07-21T15:30:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=2a9d6203d946484cbe24297fe0e48a42a800756a'/>
<id>urn:sha1:2a9d6203d946484cbe24297fe0e48a42a800756a</id>
<content type='text'>
Pylint 2.0.0 was recently released and complains more about
logging-not-lazy than it used to.  I've fixed those warnings, here.

The changes in rh_subscription are more extensive.  pylint may be
complaining incorrectly there, but the tests were not correctly un-doing
all of their mock/patching.  This cleans those up and makes pylint happy.
</content>
</entry>
<entry>
<title>lxd: Delete default network and detach device if lxd-init created them.</title>
<updated>2018-06-16T02:00:15+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@ubuntu.com</email>
</author>
<published>2018-06-16T02:00:15+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4ce6720104ec92d8d7c5aa993bf7ec405a2f53db'/>
<id>urn:sha1:4ce6720104ec92d8d7c5aa993bf7ec405a2f53db</id>
<content type='text'>
Newer versions (3.0.1+) of lxd create the 'lxdbr0' network when
'lxd init --auto' is invoked.

When cloud-init is given a network configuration to pass on to
lxc and that config had no name specified or 'lxdbr0', then cloud-init
would fail to create the network as it already exists.

Similarly, we need to remove the device from the default profile
so that the attach code can work.

Also, add a _lxc method and use it to make sure we're getting the
--force-local flag everywhere.

LP: #1776958
</content>
</entry>
<entry>
<title>citest: fix remaining warnings raised by integration tests.</title>
<updated>2017-10-20T22:06:58+00:00</updated>
<author>
<name>Scott Moser</name>
<email>smoser@brickies.net</email>
</author>
<published>2017-10-20T22:05:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=c06eea972eb4b7bfa68f4f542f2fb67ea1d455ac'/>
<id>urn:sha1:c06eea972eb4b7bfa68f4f542f2fb67ea1d455ac</id>
<content type='text'>
There was fallout in a full integration test run from my adding of
test_no_warnings_in_log which asserted that there could not be a WARNING
found in the /var/log/cloud-init.log

This fixes 2 of the cases:
 * TestCommandOutputSimple had a valid WARNING written, so adjust its
   test case to allow for that.
 * TestLxdDir had a valid config in the test but the module would
   log a WARNING, so fix the module.

Also updates lxd unit tests to look for WARN themselves.
</content>
</entry>
</feed>
