(mirror of https://github.com/marekm72/vyos-cloud-init.git) https://git.amelek.net/marekm72/vyos-cloud-init.git/atom?h=crux 2019-01-23T12:20:25+00:00 2019-01-23T12:20:25+00:00 Kim Hagen kim.sidney@gmail.com 2019-01-23T12:20:25+00:00 urn:sha1:c4da1a5cddacaa7c2a15df9170f21c3fce78fb15 release 18.5 Bump the version on cloudinit/version.py to be 18.5 and update ChangeLog LP: #1808380 Conflicts: config/cloud.cfg.tmpl 2018-10-25T20:26:25+00:00 Kim Hagen kim.sidney@gmail.com 2018-10-25T20:26:25+00:00 urn:sha1:b120f4f7a670674779a93f8c882c81f44a993888 Conflicts: cloudinit/sources/DataSourceAzure.py config/cloud.cfg.tmpl integration-requirements.txt tools/read-version 2018-10-24T14:34:50+00:00 Robert Schweikert rjschwei@suse.com 2018-10-24T14:34:50+00:00 urn:sha1:e0084a599d5259e507298175dad8a1e719017895 With db50bc0d9 the sysconfig renderer was enabled for openSUSE and SUSE Linux Enterprise. This requires that cloud-init.service starts before wicked. LP: #1799709 2018-10-21T19:30:24+00:00 Kim Hagen kim.sidney@gmail.com 2018-10-21T19:30:24+00:00 urn:sha1:46678295c78dac338111ec68c4bde2e005ef4491 2018-05-14T19:38:22+00:00 Scott Moser smoser@ubuntu.com 2018-05-14T19:38:22+00:00 urn:sha1:d5374bba2f1b4607a773ebff00e1ee7d66e23033 This makes cloud-config.service (and as a result cloud-final.service) run After snap.seeded.service. This is required to ensure that pre-seeded snaps can be used by cloud-init or user-data input. The snap.seeded.service was added to snapd at:   https://github.com/snapcore/snapd/pull/5124 Note that the following would be a workaround:  snap:   commands:    00: snap wait system seed.loaded LP: #1767131 2017-12-11T21:56:14+00:00 Robert Schweikert rjschwei@suse.com 2017-11-19T20:51:24+00:00 urn:sha1:022e8688050f19977842ee807bf2e699625b2ff8 On openSUSE and SLES systemd is allowed to pull the default dependencies, thus setting "Before=basic.target" is incorrect and creates a cycle leading to the deletion of the cloud-init-local.service 2017-10-03T14:09:13+00:00 Robert Schweikert rjschwei@suse.com 2017-09-18T16:32:10+00:00 urn:sha1:7fd04255ef238e06d1d9c9a5cc35060d36d83f2b Depending on distribution the default number of tasks (threads) maybe unexpectedly low or it may be the default systemd setting (512). Setting TasksMax to "infinity" in cloud-init-final.service removes the restriction on tasks created. LP: #1717969 2017-10-02T19:27:17+00:00 Robert Schweikert rjschwei@suse.com 2017-09-24T19:10:36+00:00 urn:sha1:6f2aaf7b0fa9fd9376561e9b6233b4d36de51da1 Ordering on apt service should only be set up on Debian based distributions. This changes is really a net-zero in runtime result. But, mentioning apt on a rpm based distro could be confusing. 2017-09-21T18:15:50+00:00 Robert Schweikert rjschwei@suse.com 2017-09-21T11:38:48+00:00 urn:sha1:0451a9f60960da56e3af4f97bbcece3d98482f86 Things done here: - identify 'suse' as a variant in util.system_info and also tools/render-cloudcfg. - update systemd and cloud.cfg templates for suse specific changes. LP: #1718640 2017-09-15T17:14:18+00:00 Balint Reczey balint.reczey@canonical.com 2017-09-15T15:50:52+00:00 urn:sha1:a2f8ce9c80debdb788e7ab37401aa98c2c270f26 Revert "centos: do not package systemd-fsck drop-in." Revert "systemd: make systemd-fsck run after cloud-init.service" The systemd-fsck drop-in caused regressions by introducing ordering The change reverts the original commit that added systemd-fsck drop-in and another commit that had removed that from the centos packaging: 1f5489c258a26f4e26261c40786537951d67df1e 8a5296c41db45be3a172862f324ad44e732a2250 The result is to no longer provide the systemd-fsck drop-in. LP: #1717477