For issue https://pagure.io/koji/issue/4441

I want to make sure this won't cause any surprising issues for other users. I think it's ok, mostly thinking out loud here.

chrony-wait.service is known for slowing boot times, sometimes significantly. However, if the system has it enabled, we might as well go after it. If it isn't enabled, the after entry won't have any effect.

That is my understanding regarding the logic for chrony-wait.service as well.

There are also systemd-timesyncd.service and systemd-time-wait-sync.service which I think have a similar relationship to chronyd and chrony-wait but I have not tested those. I am also not aware of anything that acts similar to network-online.target where it handles both NetworkManager-wait-online.service and systemd-networkd-wait-online.service without having to list each.

Commit b1e2e4b3 fixes this pull-request