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.

Bug 1951920

Summary: [RFE] Bonding: add option hwaddr
Product: Red Hat Enterprise Linux 9 Reporter: Hangbin Liu <haliu>
Component: kernelAssignee: Jarod Wilson <jarod>
kernel sub component: Bonding QA Contact: LiLiang <liali>
Status: CLOSED WONTFIX Docs Contact:
Severity: high    
Priority: high CC: jarod, liali, network-qe
Version: 9.0Keywords: FutureFeature, Triaged
Target Milestone: betaFlags: pm-rhel: mirror+
Target Release: 9.0 Beta   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-08-12 09:10:56 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:    
Bug Blocks: 1951910    

Description Hangbin Liu 2021-04-21 08:06:01 UTC 
Description of problem:

As we plan to deprecate teaming on RHEL9 and ask customers to move to bonding.
We need to fix the feature gaps between bonding and teaming. This bug is intend to add teaming feature 'hwaddr' for bonding.

hwaddr: Desired hardware address of new team device. Usual MAC address format is accepted.

This option will set team with a stable hwaddr in each mode. From sos reports there are 1298 use cases. It looks like a reasonable feature to have on bonding.
Comment 2 Hangbin Liu 2021-08-12 08:58:10 UTC 
Based on bonding doc:

8.  Where does a bonding device get its MAC address from?
---------------------------------------------------------

When using slave devices that have fixed MAC addresses, or when
the fail_over_mac option is enabled, the bonding device's MAC address is
the MAC address of the active slave.

For other configurations, if not explicitly configured (with
ifconfig or ip link), the MAC address of the bonding device is taken from
its first slave device.  This MAC address is then passed to all following
slaves and remains persistent (even if the first slave is removed) until
the bonding device is brought down or reconfigured.

If you wish to change the MAC address, you can set it with
ifconfig or ip link::

        # ifconfig bond0 hw ether 00:11:22:33:44:55

        # ip link set bond0 address 66:77:88:99:aa:bb


This means bond acts differently with team, the hwaddr will be persistent if fail_over_mac is not set. So I think there is no need to implement the 'hwaddr' option.