Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
sometimes I see an issue with nameservers not yet written into resolv.conf and activated state being reported by nmcli. This should be fixed.
Version-Release number of selected component (if applicable):
1.22
How reproducible:
ipv4_dns_resolvconf_symlinked test
Additional info:
https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-master-default-rhel8-upstream/924/artifact/artifacts/FAIL_report_NetworkManager-ci_Test307_ipv4_dns_resolvconf_symlinked.html
these are not valid as I see:
[root@wsfd-netdev34-vm-3 NetworkManager-ci]# cat /tmp/resolv.conf
# Generated by NetworkManager
search ntdv.lab.eng.bos.redhat.com
nameserver 10.19.42.41
nameserver 10.11.5.19
nameserver 10.5.30.160
[root@wsfd-netdev34-vm-3 NetworkManager-ci]# cat /tmp/resolv_orig.conf
# Generated by NetworkManager
Comment 1Beniamino Galvani
2020-03-06 13:53:20 UTC
It seems important to have this fixed in RHEL 8.3.
Since then, the test ipv4_dns_resolvconf_symlinked passes.
At the time of reporting, Vladimir also did:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/commit/1a5da593bd7a366d351b710d2e130e9eed6c8d02
so presumably that patch necessary back then to workaround this issue.
I tried now to restore the old test (from 1a5da593bd7~1). I couldn't reproduce the problem.
I also tried to change
When "nameserver" is visible with command "cat /etc/resolv.conf" in "20" seconds
to
When "nameserver" is visible with command "cat /etc/resolv.conf" in "0" seconds
(which requires https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/786).
That also didn't reproduce the issue.
So that means, the original problem is no longer reproducible, at least as far as I can tell.
I recommend to update the tests @ipv4_dns_resolvconf_symlinked and @ipv4_dns_resolvconf_file to
drop the workaround: https://gitlab.freedesktop.org/NetworkManager/NetworkManager-ci/-/merge_requests/788
In general, I think that there are some subtle issues with ordering from activated and DNS configuration.
For example, when using systemd-resolved, then DNS configuration is done asynchronously and in the background.
That means, when NM declares a profile to be activated, DNS might not yet be configured (that should be fixed).
But this bug is not about using systemd-resolved, but plain /etc/resolv.conf. In that case, NMPolicy subscribes to
NM_DEVICE_STATE_CHANGED signal before updating DNS. However, that signal is emitted before after `_notify(self, PROP_STATE);`,
so on D-Bus signal is already sent out (and theoretically could reach the client first). So there is a race, and
there is a potential problem here.
However, I would rather address this problem by the Layer3Config work and following.
Also, a theoretical issue that has no clear reproducer, is hard to address.
This rhbz was reported with a CI test failure. The CI no longer fails.
Presumably something changed in the past year.
If you still can reproduce, please reopen.