walinuxagent incorrectly complains 'WARNING Dhcp client is not running'

[Scott Moser]

fresh bionic instance on Azure, I noticed on the console
  WARNING Dhcp client is not running.

In fact there is a dhcp client running it is just not isc-dhcp.
See below.

$ systemctl status walinuxagent --no-pager --full
● walinuxagent.service - Azure Linux Agent
   Loaded: loaded (/lib/systemd/system/walinuxagent.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-01-24 18:16:07 UTC; 17min ago
 Main PID: 1058 (python3)
    Tasks: 4 (limit: 19660)
   CGroup: /system.slice/walinuxagent.service
           ├─1058 /usr/bin/python3 -u /usr/sbin/waagent -daemon
           └─1275 python3 -u bin/WALinuxAgent-2.2.20-py2.7.egg -run-exthandlers

Jan 24 18:16:11 smoser0124b python3[1058]: 0 0 ACCEPT tcp -- * * 0.0.0.0/0 168.63.129.16 owner UID match 0
Jan 24 18:16:11 smoser0124b python3[1058]: 0 0 ACCEPT tcp -- * * 0.0.0.0/0 168.63.129.16 ctstate INVALID,NEW
Jan 24 18:16:12 smoser0124b python3[1058]: 2018/01/24 18:16:11.918982 INFO Event: name=WALinuxAgent, op=ProcessGoalState, message=Incarnation 2, duration=267
Jan 24 18:16:12 smoser0124b python3[1058]: 2018/01/24 18:16:11.999610 INFO Event: name=WALinuxAgent, op=Firewall, message=, duration=0
Jan 24 18:16:12 smoser0124b python3[1058]: 2018/01/24 18:16:12.097484 INFO Set block dev timeout: sdb with timeout: 300
Jan 24 18:16:12 smoser0124b python3[1058]: 2018/01/24 18:16:12.126911 INFO Set block dev timeout: sda with timeout: 300
Jan 24 18:16:12 smoser0124b python3[1058]: 2018/01/24 18:16:12.149208 WARNING Dhcp client is not running.
Jan 24 18:16:12 smoser0124b python3[1058]: 2018/01/24 18:16:12.190923 INFO Purging disk cache, current incarnation is 2
Jan 24 18:31:10 smoser0124b python3[1058]: 2018/01/24 18:31:10.373173 INFO Agent WALinuxAgent-2.2.20 launched with command 'python3 -u bin/WALinuxAgent-2.2.20-py2.7.egg -run-exthandlers' is successfully running
Jan 24 18:31:10 smoser0124b python3[1058]: 2018/01/24 18:31:10.421698 INFO Event: name=WALinuxAgent, op=Enable, message=Agent WALinuxAgent-2.2.20 launched with command 'python3 -u bin/WALinuxAgent-2.2.20-py2.7.egg -run-exthandlers' is successfully running, duration=0

$ systemctl status systemd-networkd --no-pager --full
● systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-01-24 18:15:50 UTC; 17min ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 815 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 19660)
   CGroup: /system.slice/systemd-networkd.service
           └─815 /lib/systemd/systemd-networkd

Jan 24 18:15:50 smoser0124b systemd[1]: Starting Network Service...
Jan 24 18:15:50 smoser0124b systemd-networkd[815]: Enumeration completed
Jan 24 18:15:50 smoser0124b systemd[1]: Started Network Service.
Jan 24 18:15:50 smoser0124b systemd-networkd[815]: eth0: IPv6 successfully enabled
Jan 24 18:15:50 smoser0124b systemd-networkd[815]: eth0: Gained carrier
Jan 24 18:15:50 smoser0124b systemd-networkd[815]: eth0: DHCPv4 address 10.0.0.4/24 via 10.0.0.1
Jan 24 18:15:52 smoser0124b systemd-networkd[815]: eth0: Gained IPv6LL
Jan 24 18:16:04 smoser0124b systemd-networkd[815]: eth0: Configured

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: walinuxagent 2.2.17-0ubuntu1
ProcVersionSignature: User Name 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
Date: Wed Jan 24 18:31:35 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: walinuxagent
UpgradeStatus: No upgrade log present (probably fresh install)

[Joshua R. Poulson (jrp)]

https://github.com/Azure/WALinuxAgent/issues/1016 has been filed against the agent.

[Launchpad Janitor (janitor)]

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

[Christian Ehrhardt  (paelzer)]

The GH issue calls this closed for 18.04 - setting the bug that way.
If there is more to do that I missed please update the bug accordingly.