Comment 6 for bug 1623868

For completeness, I've attached journalctl of 2 vms.
Both are the same yakkety image, launched with no user-data within seconds of each other.
In one, systemd decided to:
   Sep 15 12:59:34 ubuntu systemd[1]: cloud-init.target: Breaking ordering cycle by deleting job cloud-final.service/start

In the other:
   Sep 15 12:59:32 ubuntu systemd[1]: multi-user.target: Breaking ordering cycle by deleting job cloud-init.target/start

Experience right now is that it is much more common for systemd to delete cloud-init.target than cloud-final.service, but both do exist.