Comment 3 for bug 1928594

While zfs-linux indeed triggers the issue, the root cause, I believe, is that automatically generated service systemd-cryptsetup@cswap wants to start after systemd-random-seed, even though it uses /dev/urandom which shouldn't require random seed data initialized. Also please note that in this particular case zfs partition is not root.