Your message dated Tue, 18 Aug 2020 11:19:10 +0000
with message-id <e1k7ze2-0001bl...@fasolo.debian.org>
and subject line Bug#968015: fixed in resolvconf 1.83
has caused the Debian Bug report #968015,
regarding resolvconf-pull-resolved.service fails with systemd 246-2
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
968015: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=968015
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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

--- End Message ---
--- Begin Message ---
Source: resolvconf
Source-Version: 1.83
Done: Dimitri John Ledkov <x...@ubuntu.com>

We believe that the bug you reported is fixed in the latest version of
resolvconf, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 968...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Dimitri John Ledkov <x...@ubuntu.com> (supplier of updated resolvconf package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 18 Aug 2020 11:56:53 +0100
Source: resolvconf
Architecture: source
Version: 1.83
Distribution: unstable
Urgency: high
Maintainer: resolvconf team <team+resolvc...@tracker.debian.org>
Changed-By: Dimitri John Ledkov <x...@ubuntu.com>
Closes: 968015
Changes:
 resolvconf (1.83) unstable; urgency=high
 .
   * Update resolvconf system units to prevent infinite restarts due to
     continious re-execution of the PathExists stanza (Closes:
     #968015). Thanks to Michael Biebl.
Checksums-Sha1:
 91e87b42e3e72b9a52193f0739e53f8f059f4d87 1716 resolvconf_1.83.dsc
 d9b0747a5f47149b988a6a855cc7cfbb587525fa 73076 resolvconf_1.83.tar.xz
 7ec41596be2d151f55fa94dfb700265ae00d8396 7213 resolvconf_1.83_source.buildinfo
Checksums-Sha256:
 09a2a54d171de24f20c04cf2588db27118a03d351cdbfecd99bddc465fc4fb9a 1716 
resolvconf_1.83.dsc
 cfb3e24510689feb9d75b040e40c4feb04defeb5f87f4a02758e3c2e2a800ecc 73076 
resolvconf_1.83.tar.xz
 749cb7dc3b60802cff232e83ad8d694c073bbee2db8debfb3e14c1f85a9294d7 7213 
resolvconf_1.83_source.buildinfo
Files:
 36ebc819347ebf8a0b2bcf098661515e 1716 net optional resolvconf_1.83.dsc
 5ba051376f89fb40fa06999b87f08bd9 73076 net optional resolvconf_1.83.tar.xz
 114ef5ed7b2d6ee3b8c7a17585a7109d 7213 net optional 
resolvconf_1.83_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE7iQKBSojGtiSWEHXm47ISdXvcO0FAl87tKMACgkQm47ISdXv
cO3UjRAAkR1i5J67MVZoypRQM9RftVRqTFjIoC5HLaufHF/HX3kdn0W3tOb7+vNn
ETv8yX2tMXj5F+OnflT/amxgzSZ66srP3D6EZAac+Kk+mGmJhMIMcmJROCmpmG2f
tbFW8GV6aHwfuDd8RfqUnGUafCJCALSSUjfLlwMOpvrZdUl6o/2Yhtri2bFwuSkW
DlHA0jL9HFwuiRe9pLGq5BDA5JfTBjlQe4wxRkWUqSQakwvvZnc82PPZz3h9Entw
TO0B90Ai1nl5wzLun7gughuFyrJc3JQCajzZHdyHLMfQ495z5Isa/IxBnm3ffWXD
yYCWu6ZhNXM0OXhVkrS8UBj2gCUCPy+JngyxzPIhPksZUn3e8vTdgCAaVpRloq0y
xxWW0x//joc0uNDSD2f6SyuqWVELGHTpWlZE+Q1i8HRX7k++mlfflHbpFUvUnYvf
e8vIMjavnJnpw8ck8liLFpAdomX4ojMxEd9Ig6ON+tJLSQ0CbdgKAxhGbNEakpqx
BcJi60pzsQ1lrff72Q57xUMu62bjRnzqGJbVSjLAnwOCii6MXzKqiUf1Oj/7ua5w
2i/8k9t2eH12/y98TqndMGqGDQjud3naf0QYJeY5HOPci46RlwXVghv4mDJ1++yN
9AxG9fANXtvbnFH/fPW4evVmnKhUXIJ8VE8P5rx2Z7uqoQ0Zl3U=
=I5R9
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to