I switched the lines from the command above for the local series
variable, and now the test passes:
autopkgtest [17:48:12]: test lxd: [-----------------------
II: Auto-init LXD...
qemu-system-x86_64: Slirp: external icmpv6 not supported yet
II: Creating Fan Bridge...
configuring fan underlay:10.0.0.0/16 overlay:250.0.0.0/8
II: Create LXD profile for Fan Bridge...
configuring LXD for underlay:10.0.0.0/16 overlay:250.0.0.0/8 (fan-250)
Profile fan-250 created
II: Test LXD...
master: detected primary route through ens3
master: DNS: systemd(10.0.2.3)
local lxd test: creating test container (Ubuntu:20.04) ...
Creating fanatic-test
Starting fanatic-test
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
slave: detected primary route through eth0
slave: waiting for systemd resolver...
sd_bus_open_system: No such file or directory
slave: DNS: systemd(250.2.15.1)
test master: ping test (250.2.15.202) ...
test slave: ping test (250.2.15.1) ...
test master: ping test ... PASS
test master: short data test (250.2.15.1 -> 250.2.15.202) ...
test slave: ping test ... PASS
test slave: short data test (250.2.15.202 -> 250.2.15.1) ...
test master: short data ... PASS
test master: long data test (250.2.15.1 -> 250.2.15.202) ...
test slave: short data ... PASS
test slave: long data test (250.2.15.202 -> 250.2.15.1) ...
test slave: long data ... PASS
test master: long data ... PASS
local lxd test: destroying test container ...
local lxd test: test complete PASS (master=0 slave=0)
II: Undefining LXD profile for Fan Bridge...
de-configuring LXD underlay:10.0.0.0/16 overlay:250.0.0.0/8
Profile fan-250 deleted
fan-250: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1450
inet 250.2.15.1 netmask 255.0.0.0 broadcast 0.0.0.0
inet6 fe80::e493:42ff:fed3:34ec prefixlen 64 scopeid 0x20<link>
ether e6:93:42:d3:34:ec txqueuelen 1000 (Ethernet)
RX packets 5684 bytes 166505628 (166.5 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 5922 bytes 167845841 (167.8 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
II: Removing Fan Bridge...
de-configuring fan underlay:10.0.0.0/16 overlay:250.0.0.0/8
PASS
autopkgtest [17:49:19]: test lxd: -----------------------]
autopkgtest [17:49:20]: test lxd: - - - - - - - - - - results - - - - - - - -
- -
lxd PASS
autopkgtest [17:49:21]: @@@@@@@@@@@@@@@@@@@@ summary
command1 PASS
lxd PASS
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1995260
Title:
dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug
Status in dnsmasq package in Ubuntu:
Fix Released
Status in dnsmasq source package in Focal:
Fix Committed
Bug description:
[SRU]
[ Impact ]
Sometimes dnsmasq is incorrectly returning NODATA instead of NXDOMAIN.
This can lead to erroneous actions by clients who need to determine
whether a domain name exists or not.
[ Test Plan ]
In a focal VM, install dnsmasq (apt install dnsmasq) if it wasn't
installed yet.
#0 Disabling systemd-resolved service and enabling resolution through
dnsmasq.
# systemctl disable --now systemd-resolved.service
# rm -f /etc/resolv.conf
# cat > /etc/resolv.conf << __EOF__
nameserver 8.8.8.8
__EOF__
# systemctl start dnsmasq.service
#1 Bad case
# for i in srv txt aaaa a aaaa a txt srv; do host -t $i test.foo. 127.0.0.1 |
tail -n 1; done
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
test.foo has no A record
Host test.foo. not found: 3(NXDOMAIN)
test.foo has no A record
test.foo has no TXT record
test.foo has no SRV record
#2 Good case
#2.1 Installing new package
# ls -1 *.deb
dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb
dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb
dnsmasq_2.80-1.1ubuntu1.6_all.deb
# dpkg -i *.deb
(Reading database ... 32073 files and directories currently installed.)
Preparing to unpack dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb ...
Unpacking dnsmasq-base (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
Selecting previously unselected package dnsmasq-utils.
Preparing to unpack dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb ...
Unpacking dnsmasq-utils (2.80-1.1ubuntu1.6) ...
Preparing to unpack dnsmasq_2.80-1.1ubuntu1.6_all.deb ...
Unpacking dnsmasq (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
Setting up dnsmasq-base (2.80-1.1ubuntu1.6) ...
Setting up dnsmasq-utils (2.80-1.1ubuntu1.6) ...
Setting up dnsmasq (2.80-1.1ubuntu1.6) ...
Processing triggers for dbus (1.12.16-2ubuntu2.3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for systemd (245.4-4ubuntu3.18) ...
# dpkg -l | grep dnsmasq
ii dnsmasq 2.80-1.1ubuntu1.6 all
Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-base 2.80-1.1ubuntu1.6 amd64
Small caching DNS proxy and DHCP/TFTP server
ii dnsmasq-utils 2.80-1.1ubuntu1.6 amd64
Utilities for manipulating DHCP leases
#2.2 Testing OK
# for i in srv txt aaaa a aaaa a txt srv; do host -t $i test.foo. 127.0.0.1 |
tail -n 1; done
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
Host test.foo. not found: 3(NXDOMAIN)
[ Where problems could occur ]
It changes the program's behaviour by classifying as NXDOMAIN what
used to be NODATA in some situations, so if a user had a workaround
for this (in the form of a script or other kind of automatization) it
will probably start to malfunction.
The last rebuilding of the package for Focal was in May, so if any new
dependencies or libs have been upgraded on this Ubuntu series this can
impact the new rebuild.
[ Other Info ]
The patch is applied upstream and originated from a bug filed on
Fedora side: https://bugzilla.redhat.com/show_bug.cgi?id=1674067
[Original Report]
---------------------------------------------------
We upgraded our openstack containers which host dnsmasq services from bionic
to focal. With this we got an update of dnsmasq from 2.79 to 2.80 which
introduced a bug in our setup where dnsmasq returns NODATA instead of NXDOMAIN.
This is already fixed upstream with the following commit [1].
The Ubuntu dnsmasq 2.80 package should get a backport with a release
for the focal packages which includes this bug fix.
[1]
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1995260/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
