Source: dnspython Version: 2.0.0-1 Severity: important Hi,
In this commit: https://github.com/rthalley/dnspython/commit/03176dea4c56ede85c34cf6bec127c96c85a8bf4 we're seeing: - self.nameservers.append('127.0.0.1') + raise NoResolverConfiguration This, as a consequence, raises an error when Eventlet is imported, and if the /etc/resolv.conf doesn't contain a valid: nameserver <IP> thingy. Indeed, Eventlet apparently instanciates a resolver object at import time, which fails if /etc/resolv.conf doesn't have a valid nameserver entry. This causes all sorts if issues, like this failure to build: https://tests.reproducible-builds.org/debian/rb-pkg/bullseye/amd64/python-oslo.rootwrap.html There's about 50 packages that are having the issue, including for example Designate (that is: OpenStack DNS as a Service). We've been discussing the problem at large (in the BTS, and over IRC), and we believe it'd be nice if we could have the above change reverted in dnspython package itself. I don't believe this issue is an RC bug, but others have a different opinion, because they believe package building should always work, even with a non-valid DNS configuration in /etc/resolv.conf (which is kind of right, I agree with it in theory, but in practice I don't think this deserve such a high severity). Your thoughts? Could this be discussed with upstream? Cheers, Thomas Goirand (zigo)
