<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests, branch circinus</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=circinus</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2022-03-25T19:42:00+00:00</updated>
<entry>
<title>T2117: Cloud-init updated to 22.1</title>
<updated>2022-03-25T19:42:00+00:00</updated>
<author>
<name>zsdc</name>
<email>taras@vyos.io</email>
</author>
<published>2022-03-25T18:58:01+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=31448cccedd8f841fb3ac7d0f2e3cdefe08a53ba'/>
<id>urn:sha1:31448cccedd8f841fb3ac7d0f2e3cdefe08a53ba</id>
<content type='text'>
Merged with 22.1 tag from the upstream Cloud-init repository.

Our modules were slightly modified for compatibility with the new
version.
</content>
</entry>
<entry>
<title>sources/azure: report ready in local phase (#1265)</title>
<updated>2022-02-15T17:19:19+00:00</updated>
<author>
<name>Chris Patterson</name>
<email>cpatterson@microsoft.com</email>
</author>
<published>2022-02-15T17:19:19+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=101a62f2389a933676e9d0d20d9f59303b1f1833'/>
<id>urn:sha1:101a62f2389a933676e9d0d20d9f59303b1f1833</id>
<content type='text'>
Pre-provisioned instances report ready early in the local phase and
again in the non-local phase, during setup().  Non-PPS only reports
ready during non-local phase.

Update the process to report ready during the local phase for all
cases.  Only attempt to do so if networking is up to prevent stalling
boot. We've already waited at least 20 minutes for DHCP if we're
provisioning, or 5 minutes for DHCP on normal boot requesting updated
network configuration.

- Extend _report_ready() with pubkey_info and raise exception
  on error to consolidate reporting done in _negotiate() and
  _report_ready().

- Remove setup(), moving relevant logic into crawl_metadata().

- Move remaining _negotiate() logic into _cleanup_markers() and
  _determine_wireserver_pubkey_info().

These changes effectively fix two issues that were present:

(1) _negotiated is incorrectly set to True

When failing to report ready.  _negotiate() squashed the exception and
the return value was not checked.  This was probably masked due to the
forced removal of obj.pkl on Ubuntu instances, but would be preferable
once we start persisting it to prevent unnecessary re-negotiation.

(2) provisioning media is not ejected for non-PPS

_negotiate() did not pass iso_dev parameter when reporting ready.  The
host will ensure this operation takes place, but it is preferable to
eject /dev/sr0 from within the guest when we're done with it.

Lastly, this removes any need for lease file parsing as the wireserver
addressed is tracked for ephemeral DHCP.  A follow-up PR will remove
this now-unused logic.

Signed-off-by: Chris Patterson &lt;cpatterson@microsoft.com&gt;</content>
</entry>
<entry>
<title>sources/azure: validate IMDS network configuration metadata (#1257)</title>
<updated>2022-02-14T19:53:36+00:00</updated>
<author>
<name>Chris Patterson</name>
<email>cpatterson@microsoft.com</email>
</author>
<published>2022-02-14T19:53:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=32fcbb580d6eacb06c901bc291e0fa118bb9b646'/>
<id>urn:sha1:32fcbb580d6eacb06c901bc291e0fa118bb9b646</id>
<content type='text'>
Due to race conditions and caching, IMDS may return stale or incomplete
metadata.  Add some validation to detect these scenarios and report
appropriate telemetry.

Introduce normalize_mac_address() to allow for comparison of mac
addresses, replacing that found inline in:
_generate_network_config_from_imds_metadata()

Add validation of final fetch of IMDS metadata.

Signed-off-by: Chris Patterson &lt;cpatterson@microsoft.com&gt;</content>
</entry>
<entry>
<title>use PEP 589 syntax for TypeDict (#1253)</title>
<updated>2022-02-14T19:24:00+00:00</updated>
<author>
<name>Brett Holman</name>
<email>bholman.devel@gmail.com</email>
</author>
<published>2022-02-14T19:24:00+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=50195ec8d1052d2b7a80f47a3709ebc4e74d6764'/>
<id>urn:sha1:50195ec8d1052d2b7a80f47a3709ebc4e74d6764</id>
<content type='text'>
Use PEP 589 syntax for TypeDict annotation.

Also fixes previously broken typing MetaSchema typing implementation.</content>
</entry>
<entry>
<title>Fix extra ipv6 issues, code reduction and simplification (#1243)</title>
<updated>2022-02-14T17:00:12+00:00</updated>
<author>
<name>eb3095</name>
<email>45504889+eb3095@users.noreply.github.com</email>
</author>
<published>2022-02-14T17:00:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=470b4a574514cf87f90682ac2bdd71b5fbbe6139'/>
<id>urn:sha1:470b4a574514cf87f90682ac2bdd71b5fbbe6139</id>
<content type='text'>
Eliminated the duplicate code and now run the entire configuration
routine against both public and private interfaces.
Also addressed an inconsistency from our metadata api for ipv6
address configuration.</content>
</entry>
<entry>
<title>tests: when generating crypted password, generate in target env (#1252)</title>
<updated>2022-02-14T15:51:03+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2022-02-14T15:51:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=17818549b3dda58a907ef44ed7de9f837ad66c3c'/>
<id>urn:sha1:17818549b3dda58a907ef44ed7de9f837ad66c3c</id>
<content type='text'>
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.</content>
</entry>
<entry>
<title>sources/azure: address mypy/pyright typing complaints (#1245)</title>
<updated>2022-02-12T04:40:45+00:00</updated>
<author>
<name>Chris Patterson</name>
<email>cpatterson@microsoft.com</email>
</author>
<published>2022-02-12T04:40:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=0b41b359a70bbbf3a648862a9b849d60b9ff6c3b'/>
<id>urn:sha1:0b41b359a70bbbf3a648862a9b849d60b9ff6c3b</id>
<content type='text'>
Raise runtime errors for unhandled cases which would cause other
exceptions.  Ignore types for a few cases where a non-trivial
refactor would be required to prevent the warning.

Signed-off-by: Chris Patterson &lt;cpatterson@microsoft.com&gt;</content>
</entry>
<entry>
<title>test_apt_security: azure platform has specific security URL overrides (#1263)</title>
<updated>2022-02-11T14:34:43+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2022-02-11T14:34:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=6dc67d732a92536dd42947af60cf4bfb25411489'/>
<id>urn:sha1:6dc67d732a92536dd42947af60cf4bfb25411489</id>
<content type='text'>
Delivered in /etc/cloud/cloud.cfg.d/90-azure.cfg</content>
</entry>
<entry>
<title>tests: lsblk --json output changes mountpoint key to mountpoinst [] (#1261)</title>
<updated>2022-02-10T22:37:17+00:00</updated>
<author>
<name>Chad Smith</name>
<email>chad.smith@canonical.com</email>
</author>
<published>2022-02-10T22:37:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=deb3ae828ea88090931c4cfe47957ae044f18ca8'/>
<id>urn:sha1:deb3ae828ea88090931c4cfe47957ae044f18ca8</id>
<content type='text'>
Ubuntu Jammy output from lsblk --json now contains
'mountpoints': [...] instead of 'mountpoint' for children devs.

Let our integration test handle either case.</content>
</entry>
<entry>
<title>mounts: fix mount opts string for ephemeral disk (#1250)</title>
<updated>2022-02-10T22:09:03+00:00</updated>
<author>
<name>Chris Patterson</name>
<email>cpatterson@microsoft.com</email>
</author>
<published>2022-02-10T22:09:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=8d96687e558d87fd767bdba9dff71e406f9bcf39'/>
<id>urn:sha1:8d96687e558d87fd767bdba9dff71e406f9bcf39</id>
<content type='text'>
Fixes the spaces introduced in #1213

Signed-off-by: Chris Patterson &lt;cpatterson@microsoft.com&gt;</content>
</entry>
</feed>
