Comment 12 for bug 1843634

I do not remember the details of the change in cloud-init.service. It could be a misunderstanding of the way things were/are supposed to be ordered, then again having "After=" for the other distros is pretty darn obvious, or it could be that a loop is created. Although the creation of a loop between "After=dbus.service" and "After=wicked.service" is hard to imagine, but it will have to be tested.

The creation and wording of lp#1799709 does suggest confusion :(

In any event this is not really related to the problem that we have no DNS information. WHich this bug is really about. cloud-init should not write a resolv.conf file that is "empty" i.e. only has the comments. That's the first problem that needs to be solved.