Red Hat Bugzilla – 2005549 – Failed to bring up teaming network in kdump initrd with the error "dbus: couldn't acquire D-Bus service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied"
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.
Failed to bring up teaming network in kdump initrd with the error "dbus: couldn't acquire D-Bus service: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied"
Description of problem:
Networkmanager failed to bring up teaming network connection becaused of missing /etc/dbus-1/system.d/teamd.conf in initrd and caused the failure of vmcore dumping to remote fs,
```
This program is not intended to be run as root.
[ 2.599750] team0: Mode changed to "activebackup"
dbus: Failed to acquire org.libteam.teamd.team0: org.freedesktop.DBus.Error.AccessDenied: Request to own name refused by policy
Failed to expose dbus name.
teamd_init() failed.
Failed: Invalid argument
<warn> [1631932469.1616] device (team0): teamd process 367 quit unexpectedly; failing activation
[ 2.439787] NetworkManager[349]: <warn> [1631932469.1616] device (team0): teamd process 367 quit unexpectedly; failing activation
<info> [1631932469.1653] device (team0): state change: prepare -> failed (reason 'teamd-control-failed', sys-iface-state: 'managed')
[ 2.443744] NetworkManager[349]: <info> [1631932469.1653] device (team0): state change: prepare -> failed (reason 'teamd-control-failed', sys-iface-state: 'managed')
<info> [1631932469.1698] manager: NetworkManager state is now DISCONNECTED
[ 2.448558] NetworkManager[349]: <info> [1631932469.1698] manager: NetworkManager state is now DISCONNECTED
<warn> [1631932469.1740] device (team0): Activation: failed for connection 'team0'
[ 2.452532] NetworkManager[349]: <warn> [1631932469.1740] device (team0): Activation: failed for connection 'team0'
<info> [1631932469.1781] device (team0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
```
I notice the upstream dracut doesn't suffer from this issue because the following commit would install /etc/dbus-1/system.d/teamd.conf to initrd,
```
commit a97d2cedcf65a9a2fbff2591171f0163c7d3cb46
Author: Dusty Mabe <dusty>
Date: Thu Jun 24 14:41:08 2021 -0400
fix(network-manager): support teaming under NM+systemd
Previously when NM was run without dbus then teaming would come
up appropriately [1], but now that dbus exists we also need to
include some supporting infrastructure to allow for it to work
again.
[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/d689380cfc5734a29b1302d68027190e1a606265
diff --git a/modules.d/35network-manager/module-setup.sh b/modules.d/35network-manager/module-setup.sh
index 0b7d21ae..f8561468 100755
--- a/modules.d/35network-manager/module-setup.sh
+++ b/modules.d/35network-manager/module-setup.sh
@@ -38,6 +38,11 @@ install() {
inst "$dbussystem"/org.freedesktop.NetworkManager.conf
inst_multiple nmcli nm-online
+ # teaming support under systemd+dbus
+ inst_multiple -o \
+ "$dbussystem"/teamd.conf \
+ "$dbussystemconfdir"/teamd.conf
+
```
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Description of problem: Networkmanager failed to bring up teaming network connection becaused of missing /etc/dbus-1/system.d/teamd.conf in initrd and caused the failure of vmcore dumping to remote fs, ``` This program is not intended to be run as root. [ 2.599750] team0: Mode changed to "activebackup" dbus: Failed to acquire org.libteam.teamd.team0: org.freedesktop.DBus.Error.AccessDenied: Request to own name refused by policy Failed to expose dbus name. teamd_init() failed. Failed: Invalid argument <warn> [1631932469.1616] device (team0): teamd process 367 quit unexpectedly; failing activation [ 2.439787] NetworkManager[349]: <warn> [1631932469.1616] device (team0): teamd process 367 quit unexpectedly; failing activation <info> [1631932469.1653] device (team0): state change: prepare -> failed (reason 'teamd-control-failed', sys-iface-state: 'managed') [ 2.443744] NetworkManager[349]: <info> [1631932469.1653] device (team0): state change: prepare -> failed (reason 'teamd-control-failed', sys-iface-state: 'managed') <info> [1631932469.1698] manager: NetworkManager state is now DISCONNECTED [ 2.448558] NetworkManager[349]: <info> [1631932469.1698] manager: NetworkManager state is now DISCONNECTED <warn> [1631932469.1740] device (team0): Activation: failed for connection 'team0' [ 2.452532] NetworkManager[349]: <warn> [1631932469.1740] device (team0): Activation: failed for connection 'team0' <info> [1631932469.1781] device (team0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed') ``` I notice the upstream dracut doesn't suffer from this issue because the following commit would install /etc/dbus-1/system.d/teamd.conf to initrd, ``` commit a97d2cedcf65a9a2fbff2591171f0163c7d3cb46 Author: Dusty Mabe <dusty> Date: Thu Jun 24 14:41:08 2021 -0400 fix(network-manager): support teaming under NM+systemd Previously when NM was run without dbus then teaming would come up appropriately [1], but now that dbus exists we also need to include some supporting infrastructure to allow for it to work again. [1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/d689380cfc5734a29b1302d68027190e1a606265 diff --git a/modules.d/35network-manager/module-setup.sh b/modules.d/35network-manager/module-setup.sh index 0b7d21ae..f8561468 100755 --- a/modules.d/35network-manager/module-setup.sh +++ b/modules.d/35network-manager/module-setup.sh @@ -38,6 +38,11 @@ install() { inst "$dbussystem"/org.freedesktop.NetworkManager.conf inst_multiple nmcli nm-online + # teaming support under systemd+dbus + inst_multiple -o \ + "$dbussystem"/teamd.conf \ + "$dbussystemconfdir"/teamd.conf + ``` Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: