vyos-cloud-init.git/systemd/systemd-fsck@.service.d/cloud-init.conf, branch rolling (mirror of https://github.com/vyos/vyos-cloud-init.git)
https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling2017-09-15T17:14:18+00:00Do not provide systemd-fsck drop-in which could cause ordering cycles.2017-09-15T17:14:18+00:00Balint Reczeybalint.reczey@canonical.com2017-09-15T15:50:52+00:00urn: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
systemd: make systemd-fsck run after cloud-init.service2017-07-25T19:41:23+00:00Scott Mosersmoser@ubuntu.com2016-12-08T12:27:53+00:00urn:sha1:1f5489c258a26f4e26261c40786537951d67df1e
cloud-init.service may write filesystems (fs_setup) or re-partition
(disk_setup) disks.
If systemd-fsck is running on a device while that is occuring
then the partitioning or mkfs might fail due to the device being busy.
Alternatively, the fsck might fail and cause subsequent mount to fail.
LP: #1691489