systemd dependency loop with systemd-update-utmp.service

[Tom]

The symptom is that dbus systemd-logind audit.d and other core services are skipped for boot. The is hit only around 1%-10% of reboots.
The log message received is:

```
Sep 9 20:17:30 systemd: basic.target: Found ordering cycle on basic.target/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on sockets.target/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on dbus.socket/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on sysinit.target/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on systemd-update-utmp.service/verify-active
Sep 9 20:17:30 systemd: basic.target: Found dependency on auditd.service/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on basic.target/start
Sep 9 20:17:30 systemd: basic.target: Breaking ordering cycle by deleting job sockets.target/start
Sep 9 20:17:30 systemd: sockets.target: Job sockets.target/start deleted to break ordering cycle starting with basic.target/start
Sep 9 20:17:30 systemd: basic.target: Found ordering cycle on basic.target/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on sysinit.target/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on systemd-update-utmp.service/verify-active
Sep 9 20:17:30 systemd: basic.target: Found dependency on auditd.service/start
Sep 9 20:17:30 systemd: basic.target: Found dependency on basic.target/start
Sep 9 20:17:30 systemd: basic.target: Breaking ordering cycle by deleting job systemd-update-utmp.service/verify-active
Sep 9 20:17:30 systemd: systemd-update-utmp.service: Job systemd-update-utmp.service/verify-active deleted to break ordering cycle starting with basic.target/start
```

This issue was fixed by overriding systemd-update-utmp.service to not include After= auditd.service

This feels like a hack and rather this was fixed upstream.

Versions:
auditd: 1:2.4.5-1ubuntu2.1
systemd: 229-4ubuntu17-acquia-201712062248~ubuntu16.04.1
kernel: 4.4.0-1065-aws

[Tom (tomelliot16)]

If there is any question about the systemd version being an in house version. We only backported a bug fix from upstream. That being said it might be a cause of the issue however we only had issues with auditd and no other services, therefore we still think this bug is relevant.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.