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.
DescriptionFernando F. Mancera
2021-04-13 09:17:32 UTC
Description of problem:
Red Hat conscious language project has identified the following problematic terms:
* "master"/"slaves"
* "whitelist"/"blacklist"
The proposed replacements are:
* "controller"/"ports"
* "allowlist"/"denylist"
The goal of this ticket is to eliminate these problematic terms in the bonding and linux bridge API.
Actual results:
There are not replacements for these problematic terms.
Expected results:
There are replacements for the terms.
Comment 2Fernando F. Mancera
2021-06-02 07:51:03 UTC
Comment 8Beniamino Galvani
2021-10-13 08:58:31 UTC
Created attachment 1832535[details]
Reproducer
Verified that the new "Ports" D-Bus property and the new nm_device_get_ports() libnm function are working well. Output of the attached script:
Controller: bridge (/org/freedesktop/NetworkManager/Devices/57)
Port: bridge-port (/org/freedesktop/NetworkManager/Devices/58)
D-Bus ports: ao 1 "/org/freedesktop/NetworkManager/Devices/58"
libnm ports: bridge-port
Controller: bond (/org/freedesktop/NetworkManager/Devices/59)
Port: bond-port (/org/freedesktop/NetworkManager/Devices/60)
D-Bus ports: ao 1 "/org/freedesktop/NetworkManager/Devices/60"
libnm ports: bond-port
Controller: team (/org/freedesktop/NetworkManager/Devices/61)
Port: team-port (/org/freedesktop/NetworkManager/Devices/62)
D-Bus ports: ao 1 "/org/freedesktop/NetworkManager/Devices/62"
libnm ports: team-port
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/RHEA-2022:1985