[Bug 1775723] [NEW] Resolved resolution delay when interacting with dnsmasq
Pavel Stratil
1775723 at bugs.launchpad.net
Thu Jun 7 23:18:01 UTC 2018
Public bug reported:
After hitting a problem with lxd on a server install (see
https://github.com/lxc/lxd/issues/4631) I was adviced by Stéphane Graber
to report a bug here. The gist of the bug is the following:
- lxd snap uses internally dnsmasq
- the 18.04 server install defaults to using systemd-resolved
- upon (re)boot, the lxd stap fails to start because of systemd-resolved not resolving shortly after boot.
To keep this bug report short, please kindly refer to
https://github.com/lxc/lxd/issues/4631 for a complete set of logs and a
"how to replicate" guide.
Thanks for looking into this,
cheers, Pavel
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Tags: dnsmasq lxd systemd-resolved
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1775723
Title:
Resolved resolution delay when interacting with dnsmasq
Status in systemd package in Ubuntu:
New
Bug description:
After hitting a problem with lxd on a server install (see
https://github.com/lxc/lxd/issues/4631) I was adviced by Stéphane
Graber to report a bug here. The gist of the bug is the following:
- lxd snap uses internally dnsmasq
- the 18.04 server install defaults to using systemd-resolved
- upon (re)boot, the lxd stap fails to start because of systemd-resolved not resolving shortly after boot.
To keep this bug report short, please kindly refer to
https://github.com/lxc/lxd/issues/4631 for a complete set of logs and
a "how to replicate" guide.
Thanks for looking into this,
cheers, Pavel
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1775723/+subscriptions
More information about the foundations-bugs
mailing list