<feed xmlns='http://www.w3.org/2005/Atom'>
<title>vyos-cloud-init.git/tests/integration_tests/test_upgrade.py, branch circinus-public-unmaintained</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-public-unmaintained</id>
<link rel='self' href='https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=circinus-public-unmaintained'/>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/'/>
<updated>2022-01-19T23:43:05+00:00</updated>
<entry>
<title>integration: test against the Ubuntu daily images (#1198)</title>
<updated>2022-01-19T23:43:05+00:00</updated>
<author>
<name>Paride Legovini</name>
<email>paride.legovini@canonical.com</email>
</author>
<published>2022-01-19T23:43:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=4c7d159c3efe39860d3c01bf680ba686b87adb77'/>
<id>urn:sha1:4c7d159c3efe39860d3c01bf680ba686b87adb77</id>
<content type='text'>
Dailies are always available for stable releases and the devel release.
Moreover testing against dailies will warn us earlier about issues.</content>
</entry>
<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>Update Azure _unpickle (SC-500) (#1067)</title>
<updated>2021-10-19T19:58:56+00:00</updated>
<author>
<name>James Falcon</name>
<email>james.falcon@canonical.com</email>
</author>
<published>2021-10-19T19:58:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=150fd30ef81cea5c2b0aff5127e33a5db786aa09'/>
<id>urn:sha1:150fd30ef81cea5c2b0aff5127e33a5db786aa09</id>
<content type='text'>
When self.failed_desired_api_version was added to DataSourceAzure, the
attribute was never added to the _unpickle method using the upgrade
framework. This commit adds the attribute.

LP: #1946644</content>
</entry>
<entry>
<title>Integration test upgrades for the 21.3-1 SRU (#1001)</title>
<updated>2021-09-15T15:44:26+00:00</updated>
<author>
<name>James Falcon</name>
<email>therealfalcon@gmail.com</email>
</author>
<published>2021-09-15T15:44:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=023f97d4e64c267b8bd809510b3fc75fcb9da688'/>
<id>urn:sha1:023f97d4e64c267b8bd809510b3fc75fcb9da688</id>
<content type='text'>
* Update test_combined.py to allow either valid LXD subplatform
* Split jinja templated tests into separate module as they can be more
  fragile
* Move checks for warnings and tracebacks into dedicated utility
  function. This allows us to work around persistent and expected
  tracebacks/warnings on particular clouds.
* Update test_upgrade.py to allow either valid Azure datasource.
  /var/lib/waagent or a mounted device are both valid.
* Add specificity to test_ntp_servers.py
  Clouds will often specify their own ntp servers in the ntp
  configuration files, so make the tests manually specify their own.
* Account for additional keys on system in test_ssh_keysfiles.py
* Update tests to account for invalid cache
  test_user_events.py and test_version_change.py both have tests that
  assume we will have valid ds cache when rebooting.
  In test_user_events.py, subsequent boots should block applying
  network on boot if boot event is denied. However, if the cache is
  invalid, it is valid to apply networking config that boot.
  In test_version_change.py no cache found won't trigger the expected
  debug log. Additionally, the pickle used for that test on an older
  release triggered an unexpected issue that took a different error
  path.
* Ignore bionic in hotplug tests (LP: #1942247)
  On Bionic, we traceback when attempting to detect the hotplugged
  device in the updated metadata. This is because Bionic is
  specifically configured not to provide network metadata.
  See LP: #1942247 for more details.
* Fix date used in test_final_message.
  In test_final_message, we ensured the variable substitution works as
  expected. For $timestamp, we compared against the current date. It's
  possible for the host date to be massively different from the client
  date, so obtain date on client rather than host.
* Remove module success from lp1813396 test. Module may fail
  unrelatedly (in this case apt-get update is failing), but the test
  should still pass.
* Skip testing events if network is disabled
* Ensure we install expected version of cloud-init
  As part of test setup, we can install cloud-init from various
  sources, including PROPOSED, PPAs, etc. We were never checking that
  this install completes successfully, and on OCI, it wasn't
  completing successfully because of apt locking issues. Code has
  been updated to retry, and then fail loudly if we can't complete the
  install.
* Remove ubuntu-azure-fips metapkg which mandates FIPS-flavour kernel
  In test_lp1835584.py
* Update test_user_events.py to account for Azure behavior
  since Azure has a separate service to clear the pickled metadata
  every boot
* Change failure to warning in test_upgrade.py if initial boot errors
  If there's already a pre-existing cause for warnings or tracebacks,
  that shouldn't cause the new version to fail.
* Add retry to test_random_passwords_emitted_to_serial_console
  It's possible we haven't retrieved the entire log when the call returns,
  so retry a few times if the output isn't empty.</content>
</entry>
<entry>
<title>testing: skip upgrade tests on LXD VMs (#980)</title>
<updated>2021-08-14T03:21:52+00:00</updated>
<author>
<name>James Falcon</name>
<email>therealfalcon@gmail.com</email>
</author>
<published>2021-08-14T03:21:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=b9c96b4f4291b0b8c014817ec6047648dc83845b'/>
<id>urn:sha1:b9c96b4f4291b0b8c014817ec6047648dc83845b</id>
<content type='text'>
The issues we see on Bionic VMs don't appear anywhere else, including
when invoking kvm directly. It likely has to do with the extra
LXD agent setup happening on bionic. Given that we still have Bionic
covered on all other platforms, the risk of skipping bionic for LXD VM
tests seems low.</content>
</entry>
<entry>
<title>testing: simplify test_upgrade.py (#932)</title>
<updated>2021-07-02T23:01:58+00:00</updated>
<author>
<name>James Falcon</name>
<email>therealfalcon@gmail.com</email>
</author>
<published>2021-07-02T23:01:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=36aeb49cb966d6ab576d4ce7cd2e815079c541a3'/>
<id>urn:sha1:36aeb49cb966d6ab576d4ce7cd2e815079c541a3</id>
<content type='text'>
test_upgrade.py was outputting a ton of stuff that had to be manually
collected and verified. This commit adds more assertions to the test
and outputs directly to the logs rather than separate files.</content>
</entry>
<entry>
<title>test_upgrade: modify test_upgrade_package to run for more sources (#883)</title>
<updated>2021-04-26T20:41:50+00:00</updated>
<author>
<name>Daniel Watkins</name>
<email>oddbloke@ubuntu.com</email>
</author>
<published>2021-04-26T20:41:50+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=5c740dcf6f278a180c32863d2b4225b6db925ef0'/>
<id>urn:sha1:5c740dcf6f278a180c32863d2b4225b6db925ef0</id>
<content type='text'>
This allows us to use it when validating packages from -proposed (and
PPAs etc.).</content>
</entry>
<entry>
<title>fix error on upgrade caused by new vendordata2 attributes (#869)</title>
<updated>2021-04-19T16:31:28+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2021-04-19T16:31:28+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=d132356cc361abef2d90d4073438f3ab759d5964'/>
<id>urn:sha1:d132356cc361abef2d90d4073438f3ab759d5964</id>
<content type='text'>
In #777, we added 'vendordata2' and 'vendordata2_raw' attributes to
the DataSource class, but didn't use the upgrade framework to deal
with an unpickle after upgrade. This commit adds the necessary
upgrade code.

Additionally, added a smaller-scope upgrade test to our integration
tests that will be run on every CI run so we catch these issues
immediately in the future.

LP: #1922739</content>
</entry>
<entry>
<title>Remove wait argument from tests with session_cloud calls (#805)</title>
<updated>2021-02-09T17:03:23+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2021-02-09T17:03:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=09193e5141ca45b822617399047204abd701047e'/>
<id>urn:sha1:09193e5141ca45b822617399047204abd701047e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Remove 'remove-raise-on-failure' calls from integration_tests (#788)</title>
<updated>2021-01-26T17:25:04+00:00</updated>
<author>
<name>James Falcon</name>
<email>TheRealFalcon@users.noreply.github.com</email>
</author>
<published>2021-01-26T17:25:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.amelek.net/vyos/vyos-cloud-init.git/commit/?id=a9c904dc6438c908cd5341312311dfbbb18c81d2'/>
<id>urn:sha1:a9c904dc6438c908cd5341312311dfbbb18c81d2</id>
<content type='text'>
pycloudlib no longer raises exceptions when cloud-init fails to start,
and the API has been updated accordingly. Changes have been made to
integration tests accordingly</content>
</entry>
</feed>
