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.
Description of problem:
In some bond modes, all slaves' mac addresses are changed to an identical one. If another bond interface enslaves and copies from one of these slaves, it will take the running mac, not perm_hwaddr(original mac).
Version-Release number of selected component (if applicable):
nmstate-1.0.2-0.3.el8.noarch
nispor-1.0.1-3.el8.x86_64
NetworkManager-1.30.0-0.10.el8.x86_64
How reproducible:
100%
Steps to Reproduce:
ip link add veth0 type veth peer veth0_ep
ip link add veth1 type veth peer veth1_ep
ip link show veth1 #check the original mac of veth1
echo "interfaces:
- name: bond0
type: bond
state: up
copy-mac-from: veth0
link-aggregation:
mode: balance-xor
port:
- veth0
- veth1" | nmstatectl set
sleep 3
echo "interfaces:
- name: bond1
type: bond
state: up
copy-mac-from: veth1
link-aggregation:
mode: balance-xor
port:
- veth1" | nmstatectl set
nmstatectl show bond*,veth[01]
Actual results:
bond0, bond1, veth0 and veth1 are with same mac address(copy from veth0)
Expected results:
bond1 and veth1 should use original mac address(perm_hwaddr) of veth1
Additional info:
Hi, when veth1 was moved from bond0 to bond1, bond1 and veth1 were still using mac from veth0, not perm_hwaddr of veth1.
Please check the attachment above.
As interface managed rule changed, here's an update of reproducer, set veth managed:
ip link add veth0 type veth peer veth0_ep
ip link add veth1 type veth peer veth1_ep
nmcli dev set veth0 managed yes
nmcli dev set veth1 managed yes
ip link show veth1 #check the original mac of veth1
echo "interfaces:
- name: bond0
type: bond
state: up
copy-mac-from: veth0
link-aggregation:
mode: balance-xor
port:
- veth0
- veth1" | nmstatectl set
sleep 3
echo "interfaces:
- name: bond1
type: bond
state: up
copy-mac-from: veth1
link-aggregation:
mode: balance-xor
port:
- veth1" | nmstatectl set
nmstatectl show bond*,veth[01]
There are two type permanent MAC address in this bug:
1. Ethtool permanent MAC address which is retried from NIC driver/firmware.
2. The bond port `perm_hwaddr` property which holding the original MAC address before this port been assigned to a bond controller.
With posted patch, nmstate will prefer item 1) and use item 2) as fallback.
To test item 1), you need real NIC or e1000e in VM.
To test item 2), veth is good enough.
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 (nmstate 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-2021:4157
Description of problem: In some bond modes, all slaves' mac addresses are changed to an identical one. If another bond interface enslaves and copies from one of these slaves, it will take the running mac, not perm_hwaddr(original mac). Version-Release number of selected component (if applicable): nmstate-1.0.2-0.3.el8.noarch nispor-1.0.1-3.el8.x86_64 NetworkManager-1.30.0-0.10.el8.x86_64 How reproducible: 100% Steps to Reproduce: ip link add veth0 type veth peer veth0_ep ip link add veth1 type veth peer veth1_ep ip link show veth1 #check the original mac of veth1 echo "interfaces: - name: bond0 type: bond state: up copy-mac-from: veth0 link-aggregation: mode: balance-xor port: - veth0 - veth1" | nmstatectl set sleep 3 echo "interfaces: - name: bond1 type: bond state: up copy-mac-from: veth1 link-aggregation: mode: balance-xor port: - veth1" | nmstatectl set nmstatectl show bond*,veth[01] Actual results: bond0, bond1, veth0 and veth1 are with same mac address(copy from veth0) Expected results: bond1 and veth1 should use original mac address(perm_hwaddr) of veth1 Additional info: