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.
Request backport upstream fix https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=643d80ec913a313209ccbc5567def4b466ab546c
The problem is, you cannot *enable* connectivity-check via D-Bus, only disable.
$ busctl set-property org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager ConnectivityCheckEnabled "b" 1
This is new API, hence it's not high priority. But the fix is quite obviously correct and trivial. Hence, requesting backport of this patch.
Just calling `busctl set-property` followed by `busctl get-property` should already expose the bug.
Reproduce on older versions:
- configure in NetworkManager.conf:
[connectivity]
enabled=false
- note, that `busctl set-property ... true` cannot actually enable the setting.
Alternative to reproduce on older versions:
- note (via busctl get-property), that connectivity checking is enabled.
- disable via `busctl set-property`.
- note, that `busctl set-property ... true` cannot actually enable the setting.
Now that should work.
Note that if you overwrite the value via D-Bus, that is persisted in the file "/var/lib/NetworkManager/NetworkManager-intern.conf". This file gets merged with the files edited by user (NetworkManager.conf).
Caveat: "NetworkManager-intern.conf" is only readable by root. Hence, if you issue `/sbin/NetworkManager --print-config` as non-root, the file won't contain the setting from there. If you issue it as root, or look at what logs NM during startup, then you will see that the configuration setting got merged.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2018:0778