Package: resolvconf Version: 1.82 Since `systemd` version 246-2, systems using `systemd-resolved` fail to reach the `default.target` if `resolvconf` is also installed.
Steps to reproduce the error in a sysroot (`less` and `bash-completion` are just for comfort in debugging/reading logs): ```shell # debootstrap --variant minbase sid sid # systemd-nspawn --directory sid # apt update # apt install resolvconf systemd less bash-completion # systemctl enable systemd-networkd # systemctl enable systemd-resolved # exit # systemd-nspawn --directory sid --boot ``` With the last command `init` will try to start `resolvconf-pull-resolved.service` endlessly and not reach the `default.target`. At this point, you may no longer be able to read `systemd-nspawn`'s info in your terminal so keep in mind: > Press ^] three times within 1s to kill container. The error messages: ``` ... [FAILED] Failed to start resolvconf-pull-resolved.service. See 'systemctl status resolvconf-pull-resolved.service' for details. [FAILED] Failed to start resolvconf-pull-resolved.service. See 'systemctl status resolvconf-pull-resolved.service' for details. [FAILED] Failed to start resolvconf-pull-resolved.service. See 'systemctl status resolvconf-pull-resolved.service' for details. [FAILED] Failed to start resolvconf-pull-resolved.service. See 'systemctl status resolvconf-pull-resolved.service' for details. [FAILED] Failed to start resolvconf-pull-resolved.service. See 'systemctl status resolvconf-pull-resolved.service' for details. [FAILED] Failed to start resolvconf-pull-resolved.service. See 'systemctl status resolvconf-pull-resolved.service' for details. ... ``` This also happens on physical machines, leaving some of mine unbootable currently. :( Unfortunately I am not completely sure why the service fails as I am not familiar enough with it. This is my first Debian bug report so I hope I did it correctly. Should this bug somehow tag the Debian systemd team as well, since technically an update to the `systemd` package introduced it? A solution may be to just not install `resolvconf` but it's in the `Recommends` of a lot of other packages so it will be installed on many systems that might use `resolved`, which is already a part of the `systemd` package. Cheers, Thomas Mühlbacher
