Bug 2005549
| Summary: | 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" | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 9 | Reporter: | Coiby <coxu> |
| Component: | dracut | Assignee: | Pavel Valena <pvalena> |
| Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 9.0 | CC: | coxu, dracut-maint-list, dtardon, pvalena, rvykydal |
| Target Milestone: | rc | Keywords: | Bugfix, TestOnly, Triaged |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | dracut-057-13.git20220816.el9 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-08-17 18:35:27 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: | |||
| Bug Depends On: | 2066816 | ||
| Bug Blocks: | |||
Hello, please test, if you can, whether the planned rebase for 9.1 works for you. RPMS: https://github.com/pvalena/rpms/tree/main/dracut/2066816 *** Bug 2108486 has been marked as a duplicate of this bug. *** |
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: