Comment 12 for bug 1996007

Hello Wei WA,
such messages during boot up like "A start job is running for wait for ..."
are because a (systemd-) service takes some time to be completed.
It's probably systemd-networkd, which just may need some time - and uses 'systemd-networkd-wait-online' (maybe in combination with cloud-init, but after the post-install reboot cloud-init should be disabled, indicated by the existence of this file '/etc/cloud/cloud-init.disabled').
In case of multiple interfaces, and some without connectivity, it may wait up to 2 mins for a connection - there are different ways to prevent this potential delay ...
I see and have these messages also on my system, but there should be no harm (other than a some delay), except:
- if things break or crash while being executed
  (in this case you should find a related crash file in /var/crash)
- or if the network changes significantly
  for example you had devices during the installation that were configured,
  but are no longer available (for example in case they were removed from the LPAR config in DPM)
  In this case the yaml need to be cleaned-up or at least 'optional: true' added
  to the(temporarily) missing interface in the yaml.
- or - sometimes in case of ipv6 is enabled in your environment (saw that once) -
  there can be an issue getting network config bits fast enough (e.g. in case of 'dhcpv6').
  To figure that out, try to temp. disable ipv6.

And what I forgot to mention (well, maybe too obvious) systemd-networkd must be active and running:
'sudo systemctl status systemd-networkd'