Comment 10 for bug 1843634

Actually cloud-init.service has "Before=wicked.service" when I changed it to "After=wicked.service", the eth0 interface was brought up without me explicitly bringing it up. I'm attaching the logs for that VM.
When I checked the "cloud-init.service" file in cloud-init 18.2, It had "After=wicked.service" but in 18.5 and 19.1 it has "Before=wicked.service". I brought up this point before in an offline discussion with Robert and he indicated that in 18.5 a dependency of cloud-init on dhcp-client was added to support the process flow intended by upstream and support dynamic network configuration via cloud-init.
@Robert, can you please elaborate more on that?