After introduction of [vyos-hostsd.service](https://github.com/vyos/vyos-build/commit/372bad3d5d11572142443dfd7c4b28827bbde458) systemd started to complain about dependency cycle during early boot: `Ordering cycle found, skipping LSB: Raise network interfaces`, which corresponds to `/etc/init.d/networking` service
{F400766}
Here is an excerpt from journald:
```
Sep 01 12:48:28 vyos systemd[1]: systemd 215 running in system mode. (+PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ -SECCOMP -APPARMOR)
Sep 01 12:48:28 vyos systemd[1]: Detected virtualization 'kvm'.
Sep 01 12:48:28 vyos systemd[1]: Detected architecture 'x86-64'.
Sep 01 12:48:28 vyos systemd[1]: Inserted module 'autofs4'
Sep 01 12:48:28 vyos systemd[1]: Set hostname to <vyos>.
Sep 01 12:48:28 vyos kernel: random: systemd-sysv-ge: uninitialized urandom read (16 bytes read)
Sep 01 12:48:28 vyos kernel: random: systemd-sysv-ge: uninitialized urandom read (16 bytes read)
Sep 01 12:48:28 vyos systemd[1]: Cannot add dependency job for unit display-manager.service, ignoring: Unit display-manager.service failed to load: No such file or directory.
Sep 01 12:48:28 vyos systemd[1]: Found ordering cycle on basic.target/start
Sep 01 12:48:28 vyos systemd[1]: Found dependency on sysinit.target/start
Sep 01 12:48:28 vyos systemd[1]: Found dependency on networking.service/start
Sep 01 12:48:28 vyos systemd[1]: Found dependency on network-pre.target/start
Sep 01 12:48:28 vyos systemd-journal[491]: Journal started
...
```
The first rolling image with this warning is `vyos-1.2-rolling-201908222129-amd64.iso`, and persists till today's one `vyos-1.2-rolling-201909011324-amd64.iso`