Bug 1436770
Summary: | NetworkManager service restart is required after FirewallD package installation to get active zone | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Lev Veyde <lveyde> | |
Component: | NetworkManager | Assignee: | Thomas Haller <thaller> | |
Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | |
Severity: | high | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 7.3 | CC: | atragler, bgalvani, fgiudici, lrintel, lveyde, mleitner, rkhan, sukulkar, thaller, todoleza, twoerner, vbenes | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | NetworkManager-1.8.0-1.el7 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1444471 (view as bug list) | Environment: | ||
Last Closed: | 2017-08-01 09:24:38 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: |
Description
Lev Veyde
2017-03-28 15:36:41 UTC
The firewalld service is not started automatically after installation of the firewalld package. Because of this I do not understand why firewalld should restart NetworkManager in the firewalld installation process. Restarting NetworkManager might result in a connection loss, therefore this is something that should not be done in my opinion. Maybe the NetworkManager team could reveal why the access to the firewalld D-Bus interface is an issue here as the error is happening in NetworkManager. (In reply to Thomas Woerner from comment #3) > The firewalld service is not started automatically after installation of the > firewalld package. Because of this I do not understand why firewalld should > restart NetworkManager in the firewalld installation process. > > Restarting NetworkManager might result in a connection loss, therefore this > is something that should not be done in my opinion. > > Maybe the NetworkManager team could reveal why the access to the firewalld > D-Bus interface is an issue here as the error is happening in NetworkManager. Hi Thomas, The end result is that FirewallD (firewall-cmd) doesn't properly return information, and I'm not entirely sure for the reason. It would be nice if you could debug it from your side, to get more information, including more details where the request fails exactly, and so, if after that you're 100% certain that the issue is not in the FirewallD, but in the NetworkManager code, it would be easier for them to pinpoint the issue, and hopefully also get a faster resolution. The problem is that NM does not react when firewalld is appearing later. It's an NM bug. Reassigning. Seems the problem is that dbus-daemon remembers that the NetworkManager process is not allowed to talk to firewalld. Later, when firewalld is installed, dbus-daemon still rejects the currently running NM process until it is restarted. See also: - bug 1109513 (grep for "This introspection is prohibited by dbus-daemon") Fixed upstream: master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=cc1d409ba886e8e7c33f845790cfc700fcd2d854 nm-1-8: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=ff5b7275a7584fcdabe4327f1a061c5610cf89dd 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/RHSA-2017:2299 |