This bug was fixed in the package systemd - 237-3ubuntu10.23
---
systemd (237-3ubuntu10.23) bionic; urgency=medium
* d/p/resolved-do-not-hit-CNAME-in-NODATA.patch:
- fix stub resolver cache (LP: #1818527)
-- Heitor Alves de Siqueira Tue, 04 Jun 2019
15:54:24 -0300
** Change
Some comments on the Autopkgtest regressions:
- lxc (armhf) fails due to the ftpmaster.internal mirror failing
- libvirt (armhf) fails for the same reason ("Unable to connect to
ftpmaster.internal:http")
- systemd (ppc64el) has been failing since before this patch was
introduced, and looking at
Verified for Bionic:
ubuntu@bionic:~$ dpkg -l | grep systemd
ii systemd 237-3ubuntu10.23
amd64system and service manager
ubuntu@bionic:~$ systemd-resolve --flush-caches
ubuntu@bionic:~$ dig +noall +answer github.com CNAME
ubuntu@bionic:~$
Hello Abam, or anyone else affected,
Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.23 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Description changed:
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific
domain, further attempts at resolving A records for that same domain fail.
This has been fixed upstream in v240.
Upst
Sponsored in Bionic.
* The fix LGTM.
- Looking in systemd git upstream repo, I couldn't find anything (revert, known
regression introduced by this particular fix or else)
- I easily reproduced the bug using systemd without the fix, and I confirm it
works for both enumerated scenarios found in [
** Tags removed: ddstreet-next sts-sponsor-ddstreet
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818527
Title:
Stub resolver cache is corrupted
To manage notifications about this bug go to:
https
** Description changed:
[Impact]
systemd-resolved fails to resolve A records
[Description]
When systemd-resolve caches a non-existent CNAME record for a specific
domain, further attempts at resolving A records for that same domain fail.
This has been fixed upstream in v240.
Upst
** Tags added: systemd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818527
Title:
Stub resolver cache is corrupted
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/
I can include this in my next systemd upload, once the current -proposed
versions are released.
** Tags added: sts-sponsor-ddstreet
** Tags added: ddstreet-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
[sts-sponsor]
There is an SRU in progress for systemd already for Bionic. It will have
to wait for LP: #1814373 and #1825997 to be 'Fix Released' before
sponsoring that particular bug.
Thanks Heitor for your contribution.
Let's circle back later.
- Eric
--
You received this bug notification b
** Description changed:
+ [Impact]
+ systemd-resolved fails to resolve A records
+
+ [Description]
+ When systemd-resolve caches a non-existent CNAME record for a specific
domain, further attempts at resolving A records for that same domain fail.
This has been fixed upstream in v240.
+
+ Upst
** Also affects: systemd (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: systemd (Ubuntu)
Status: Confirme
This bug also affects MaaS when commissioning is done with Bionic 18.04
and an external proxy is set.
Commissioning fails at the step inside the script when trying to install packages for the test itself.
Error message:
Temporary failure resolving
--
You received this bug notification becaus
This seems to be the same issue previously reported at
https://github.com/systemd/systemd/issues/9833, which was fixed in
https://github.com/systemd/systemd/pull/9836 (commit 3740146) and
released in v240.
** Bug watch added: github.com/systemd/systemd/issues #9833
https://github.com/systemd/sy
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818527
Title:
St
16 matches
Mail list logo