(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=current 2017-07-19T21:52:32+00:00 2017-07-19T21:52:32+00:00 Ryan Harper ryan.harper@canonical.com 2017-06-13T14:06:41+00:00 urn:sha1:dcbe479575fac9f293c5c4089f4bcb46ab887206 Under el7, cloud-init systemd files need some unit tweaks to ensure they run at the right time. Pull in current el7 downstream systemd unit changes. 2017-06-13T14:39:31+00:00 Scott Moser smoser@brickies.net 2017-06-12T18:10:58+00:00 urn:sha1:11121fe4d5af0554140d88685029fa248fa0c7c9 This changes all cloud-init systemd units to run 'Before' the apt processes that run daily and may cause a lock on the apt database. apt-daily-upgrade.service contains 'After=apt-daily.service'. Thus following order is enforced, so we can just be 'Before' the first. apt-daily.service apt-daily-upgrade.service Note that this means only that apt-daily* will not run until cloud-init has entirely finished. Any other processes running apt-get operations are still affected by the global lock. LP: #1693361 2016-09-09T19:58:30+00:00 Scott Moser smoser@brickies.net 2016-09-08T17:17:37+00:00 urn:sha1:34a26f7f59f2963691e36ca0476bec9fc9ccef63 In systemd, package installation before the system is fully booted (systemctl is-system-running == starting) may result in the package not being started. Upgrade (package_upgrade: true) can also cause failure if that is done during systemd boot. The solution here is: a.) move config modules that do or may do package installation to 'final_modules'. That list is: - snappy - package-update-upgrade-install - fan - landscape - lxd - puppet - chef - salt-minion - mcollective b.) move cloud-final.service to run as 'Type=idle' LP: #1576692, #1621336 2016-04-04T20:07:07+00:00 Scott Moser smoser@ubuntu.com 2016-04-04T20:07:07+00:00 urn:sha1:35802e8866be53016779f4f1eae9f026ccd18a61 syslog.target is obsolete in debian, this fixes a lintian warning. LP: #1536964 2016-03-01T04:10:44+00:00 Scott Moser smoser@ubuntu.com 2016-03-01T04:10:44+00:00 urn:sha1:2a73e674605916077cf6a87410f4ad0829938400 This adds cloud-init.target which is a single target to encompass all the services of cloud-init. 2015-11-30T20:33:28+00:00 Scott Moser smoser@ubuntu.com 2015-11-30T20:33:28+00:00 urn:sha1:f512c0126aac5c8708065c6e8aa5510f83574657 if a runcmd exited failure, then power_state would not work. This was because systemd was killing off subprocesses, and cloud-init implemented power off with a subprocess that waited for the parent to exit. LP: #1449318 2015-04-09T15:54:01+00:00 Scott Moser smoser@ubuntu.com 2015-04-09T15:54:01+00:00 urn:sha1:f4789639af50ea631cf75af526ad013b05670caa don't declare a Wants/Requires on network.target; this is a passive target that should only be pulled in by implementors of the networking service. The requirement for network needs to be expressed as a dependency on network-online.target. LP: #1440180 2015-03-17T19:50:00+00:00 Scott Moser smoser@ubuntu.com 2015-03-17T19:50:00+00:00 urn:sha1:ccdf4ff9966b020a8fd30e5bec87fa82dc20c214 LP: #1432758 2013-09-20T23:04:49+00:00 Garrett Holmstrom gholms@eucalyptus.com 2013-09-20T23:04:49+00:00 urn:sha1:4050105c1cfb100e6b93c56a74ecd2fe29d87608 that device and write to it directly things can start going haywire. Here we address this problem by sending console-bound output to stdout and letting init take care of getting it to the console instead. We already configure upstart with "console output", so we need only change systemd to use "journal+console". 2012-08-03T21:40:42+00:00 Garrett Holmstrom gholms@eucalyptus.com 2012-08-03T21:40:42+00:00 urn:sha1:3ac504a49a3755e58f6e74b7a17f98f3d4a4eb0c