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.
NetworkManager's team plugin talks to teamd via D-Bus.
Either that should be fixed, to optionally talk to teamd via the unix-socket (which it also supports). Honestly, I don't think this is the right solution. D-Bus for us is just the IPC, and this IPC solution should be so ubiquitous and work everywhere (including initrd). While it would be relatively simple to switch team support to unix socket, there is a slur of other things that also won't work in initrd (e.g. we won't be able to talk to supplicant). Of course, all of these features have low priority, so it means initrd stays fundamentally limited.
Anyway, as it is, team support with NetworkManager won't work from initrd, because D-Bus is not running. We should not package it.
https://github.com/dracutdevs/dracut/blob/958ca9e912d3a3a1ebe79a8d4fc36de2a60e4381/modules.d/35network-manager/module-setup.sh#L37
Comment 2Beniamino Galvani
2020-05-21 20:24:23 UTC
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 (NetworkManager bug fix and enhancement update), 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-2020:4499
Requesting backport to 8.2.z
We have a report of a user hitting this issue when using OCP/RHCOS 4.6, which is using RHEL 8.2 EUS content. See: https://bugzilla.redhat.com/show_bug.cgi?id=1986921
OCP 4.6 is an EUS release and will continue to use RHEL 8.2 EUS content for the extent of it's lifetime, so there is no chance of using a newer version of RHEL content in OCP/RHCOS 4.6.
As such, we would like to see this fix backported so that we may unblock users that are utilizing teaming configurations as part of their initial network bringup.