Comment 10 for bug 1964686

On Friday, March 18 2022, Romain Geissler wrote:

> I could successfully validate that the fix works. I initially installed
> the current official jammy package, it was hanging again, then I
> installed your ppa repo and upgraded the packages, and it worked. See
> the following relevant part of my testing (ran in Docker):
>
> Setting up liblmdb0:amd64 (0.9.24-1build1) ...
> Setting up libmaxminddb0:amd64 (1.5.2-1build1) ...
> Setting up libnghttp2-14:amd64 (1.43.0-1build2) ...
> Setting up libuv1:amd64 (1.43.0-1) ...
> Setting up libmd0:amd64 (1.0.4-1) ...
> Setting up libbsd0:amd64 (0.11.5-1) ...
> Setting up libjson-c5:amd64 (0.15-2build3) ...
> Setting up libicu70:amd64 (70.1-2) ...
> Setting up libedit2:amd64 (3.1-20210910-1) ...
> Setting up libxml2:amd64 (2.9.13+dfsg-1) ...
> Setting up bind9-libs:amd64 (1:9.18.0-2ubuntu2) ...
> Setting up bind9-host (1:9.18.0-2ubuntu2) ...
> Setting up bind9-dnsutils (1:9.18.0-2ubuntu2) ...
> Setting up dnsutils (1:9.18.0-2ubuntu2) ...
> Processing triggers for libc-bin (2.35-0ubuntu3) ...
> root@9245c5040595:/# host some-host
> (hangs forever, I interrupted the command)
>
>
> root@9245c5040595:/# add-apt-repository ppa:sergiodj/bind9-lp1964686
> Repository: 'deb https://ppa.launchpadcontent.net/sergiodj/bind9-lp1964686/ubuntu/ jammy main'
> More info: https://launchpad.net/~sergiodj/+archive/ubuntu/bind9-lp1964686
> Adding repository.
> Press [ENTER] to continue or Ctrl-c to cancel.
> Adding deb entry to /etc/apt/sources.list.d/sergiodj-ubuntu-bind9-lp1964686-jammy.list
> Adding disabled deb-src entry to /etc/apt/sources.list.d/sergiodj-ubuntu-bind9-lp1964686-jammy.list
> Adding key to /etc/apt/trusted.gpg.d/sergiodj-ubuntu-bind9-lp1964686.gpg with fingerprint 1D66A93D45649FD3B4319D337CD01F95D2AA1673
> Hit:1 http://archive.ubuntu.com/ubuntu jammy InRelease
> Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease
> Hit:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease
> Hit:4 http://archive.ubuntu.com/ubuntu jammy-backports InRelease
> Get:5 https://ppa.launchpadcontent.net/sergiodj/bind9-lp1964686/ubuntu jammy InRelease [18.1 kB]
> Get:6 https://ppa.launchpadcontent.net/sergiodj/bind9-lp1964686/ubuntu jammy/main amd64 Packages [2214 B]
> Fetched 20.3 kB in 1s (14.8 kB/s)
> Reading package lists... Done
> root@9245c5040595:/# apt-get upgrade
> Reading package lists... Done
> Building dependency tree... Done
> Reading state information... Done
> Calculating upgrade... Done
> The following packages will be upgraded:
> bind9-dnsutils bind9-host bind9-libs dnsutils libudev1 login passwd
> 7 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
> Need to get 2595 kB of archives.
> After this operation, 0 B of additional disk space will be used.
> Do you want to continue? [Y/n] y
> Get:1 http://archive.ubuntu.com/ubuntu jammy/main amd64 login amd64 1:4.8.1-2ubuntu2 [187 kB]
> Get:2 https://ppa.launchpadcontent.net/sergiodj/bind9-lp1964686/ubuntu jammy/main amd64 bind9-host amd64 1:9.18.0-2ubuntu4 [83.7 kB]
> Get:3 http://archive.ubuntu.com/ubuntu jammy/main amd64 libudev1 amd64 249.11-0ubuntu1 [77.1 kB]
> Get:4 http://archive.ubuntu.com/ubuntu jammy/main amd64 passwd amd64 1:4.8.1-2ubuntu2 [767 kB]
> Get:5 https://ppa.launchpadcontent.net/sergiodj/bind9-lp1964686/ubuntu jammy/main amd64 bind9-dnsutils amd64 1:9.18.0-2ubuntu4 [189 kB]
> Get:6 https://ppa.launchpadcontent.net/sergiodj/bind9-lp1964686/ubuntu jammy/main amd64 bind9-libs amd64 1:9.18.0-2ubuntu4 [1248 kB]
> Get:7 https://ppa.launchpadcontent.net/sergiodj/bind9-lp1964686/ubuntu jammy/main amd64 dnsutils all 1:9.18.0-2ubuntu4 [43.7 kB]
> Fetched 2595 kB in 1s (3081 kB/s)
> ...
>
> root@9245c5040595:/# host some-host
> Host some-host not found: 2(SERVFAIL)
> root@9245c5040595:/#

Thank you for verifying this.

> About reproducing the original issue, I don't really know how to do
> it. I tried starting the container with "--dns 8.8.8.8" and this was
> enough to fix the issue with the current official jammy package. I
> also tried with two DNS (8.8.8.8 and 8.8.4.4). I don't know what is so
> special about our corporate DNS.

Yeah; as far as I've read in the upstream's bug report, this issue can
be a bit tricky to reproduce.

> Since I could validate the fix on my side, will this land in an official
> jammy package update before the official release of jammy in april ?

This patchset also fixes another bind9 issue we're seeing (bug
#1964400), so yeah, I intend to work on doing a more formal backport of
the upstream patches and filing an MP for it next week.

Thanks again for the help in verifying the fix.

--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14