commit 3705bb5964a2ff3f9a67265e6d090a112b35e40c (HEAD -> bug/1623868)
Author: Scott Moser <smoser@brickies.net>
Date:   Thu Sep 15 09:30:50 2016 -0400

    systemd: put cloud-init.target After multi-user.target
    
    When we moved cloud-final.service to run After multi-user.target it
    caused a dependency loop (as cloud-init.target was still implied to be
    Before multi-user.target).
    
    journalctl would either show:
      cloud-init.target: Breaking ordering cycle by deleting job
         cloud-final.service/start
    or
      multi-user.target: Breaking ordering cycle by deleting job
         cloud-init.target/start
    
    The fix here is to clearly state that cloud-init.target is also
      After multi-user.target
    
    LP: #1623868

diff --git a/systemd/cloud-init.target b/systemd/cloud-init.target
index a63babb..d568458 100644
--- a/systemd/cloud-init.target
+++ b/systemd/cloud-init.target
@@ -4,3 +4,4 @@
 #  b.) touch a file /etc/cloud/cloud-init.disabled
 [Unit]
 Description=Cloud-init target
+After=multi-user.target