OK, then this is actually no regression. Closing ...
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Invalid
** Changed in: network-manager (Ubuntu Bionic)
Status: Incomplete => Invalid
** Tags removed: bionic regression-proposed
--
You received this bug
Thank you very much for your great cooperation. I wish other bug
reporters do so, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
network-manager 1.10.14-0ubuntu2 ignores
Correct, the "regression", such as it was, seemingly exists only as a
change to how that invalid systemd-resolved conf was handled. I did go
back and verify that the invalid config did function on the old version,
but no on the new, so there is a functional change there, but given the
invalidity
Does this mean that for you there is now no regression in the Bionic SRU
of Network Manager (1.10.14-0ubuntu2)? Can I mark this bug report as
"Invalid" then?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well ... that configuration correction appears to have done the trick!
I'm very sorry to have inadvertently put you through this for the sake
an off-by-one-character invalid config. Re-reading the documentation I
can now see where the confusion occurred when crafting the config
originally, and I
Best would even be if you could run the tests as shown in the "[Test
case]" section of the description of bug 1754671, but in addition
capture the full journal with all messages of systemd-resolved.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please also run the command
systemd-resolve --status
and post the output here for each of your tests.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
network-manager 1.10.14-0ubuntu2
Sorry, I've been a bit swamped and this fell through the cracks, I'll
try and find some time this week to try with the updated config.
In answer to your previous question: yes, the dig was the first thing I
did following a reboot each time with the intention of providing the
smallest number of
Mal, regarding your log files of comments #12 and #13, did you do the
booting and the dig commands in less than 1 minute for each NM version?
Each of the logs spans a time frame of little less than 1 minute?
Could you also repeat your tests after correcting your configuration
according to comment
Mal, could you also provide logs of sytemd-resolved (if needed complete
journal) for your tests?
** Changed in: network-manager (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I asked on the upstream mailing list and got the following answer:
--
Hi,
the domain specification in the configuration reported on launchpad:
[Resolve]
Cache=no
DNS=127.0.0.54
Domains=~.local.org.com
is invalid:
systemd-resolved[13415]: Failed to add search domain
** Changed in: network-manager (Ubuntu Bionic)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
network-manager
Here you are, Till. Three sections, one for each NM version containing
the two dig requests during the tests, plus one for a dig to contact the
local DNS explicitly.
nm-1.10.6:
$ dig dnsmasq.local.org.com | grep -FA1 ';; ANSWER' # first attempt always fails
;; ANSWER SECTION:
Some clarification:
1. dns-priority=-1 used to work (openvpn had highest DNS priority over other
connections) before the regression happend.
2. I rebooted my system after changing config to dns-search=~
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have some extra information that might lead you into the right
direction.
I used the following extra line in my openvpn connection config file
(/etc/NetworkManager/system-connections/vpn_connection_name):
[ipv4]
dns-priority=-1
After the update DNS received from OpenVPN connection was not
Mal, thanks for the logs, could you tell me, to make it easier for me to
find what went wrong, tell me which host names you queried with "dig",
which IP they should return, and through which DNS? Thank you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Tags removed: regression-update
** Tags added: regression-proposed
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Triaged
** Changed in: network-manager (Ubuntu Bionic)
Status: Incomplete => Triaged
--
You received this bug notification because you are a member
Process follows directly from previous comment.
- Updated to network-manager 1.10.14-0ubuntu2 (from bionic-proposed)
- Rebooted and ran dig twice to mirror previous test, never resolved to
expected result. :(
- Log file from reboot until after the second dig attached.
Ran dig a few more times
Can only attach one file at a time, so this and the next comment are
heavily linked.
- Updated to systemd 237-3ubuntu10.22 (from bionic-updates)
- Enabled debug logging for network manager and disabled flood protection on
journald.
- Rebooted and successfully ran dig (second attempt)
- First
The SRU for systemd has arrived in bionic-proposed (see bug 1754671).
Could you make sure that you have installed BOTH the network-manager and
systemd SRUs from bionic-proposed (to make sure that I did not perhaps
do something wrong with the systemd update in my PPA). Versions should
be:
Sorry there was a part missing. Let us try again:
Please create the following files (and directories if needed for them):
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
1. /etc/systemd/journald.d/noratelimit.conf containing
RateLimitIntervalSec=0
RateLimitBurst=0
2. /etc/NetworkManager/conf.d/debug.conf
[logging]
level=TRACE
domains=ALL
Then restart journald:
sudo systemctl restart systemd-journald
and NetworkManager:
sudo systemctl restart network-manager
I am rather new to network-manager internals, but could you try the
command
sudo nmcli con modify "$COMPANY VPN" ipv4.dns-priority -1 ipv4.dns-
search ~.
Does this solve your problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: network-manager (Ubuntu Bionic)
Status: Incomplete => Confirmed
** Changed in: network-manager (Ubuntu Bionic)
Importance: Undecided => High
** Tags added: bionic
--
You received this bug
Installed the systemd from the ppa and the .14 NM package:
ii network-manager 1.10.14-0ubuntu2
ii systemd 237-3ubuntu10.22~ppa1
Rebooted, gave it a spin and no good, I'm afraid. The 127.0.0.54
resolver was still left out of the loop. I've since gone back to the
public systemd
Due to the SRU regressions reported in LP: #1829838 and LP: #1829566, I
have reverted this SRU for the moment, restoring network-manager
1.10.6-2ubuntu1.1 to bionic-updates.
network-manager 1.10.14-0ubuntu2 remains available in bionic-proposed
for testing purposes.
--
You received this bug
Unfortunately, the SRU for systemd did not yet get processed. Therefore
I have now uploaded this version of systemd to my PPA:
https://launchpad.net/~till-kamppeter/+archive/ubuntu/ppa
Please follow this link, follow the instructions in the section "Adding
this PPA to your system", then update
Yup, it shows up at the top of the global resolver list:
$ systemd-resolve --status
Global
Are these DNS servers listed in the output of
systemd-resolve --status
If yes, could you try the updated network-manager in combination with
the proposed systemd update of bug 1754671?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Looks like that the new version of network-manager is not working
correctly with the systemd-resolved of Bionic.
** Tags added: regression-update
** Also affects: network-manager (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a
** Changed in: network-manager (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
network-manager 1.10.14-0ubuntu2 ignores systemd-resolved
I have a similar setup and am experiencing the same thing since the
update. Thanks for narrowing it down to network-manager!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829566
Title:
32 matches
Mail list logo
