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 2143768 - Support cloned MAC address
Summary: Support cloned MAC address
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: rhel-system-roles
Version: 9.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 9.2
Assignee: Rich Megginson
QA Contact: Jon Trossbach
Mayur Patil
URL:
Whiteboard: role:network
Depends On: 2143458
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-11-17 19:17 UTC by Wen Liang
Modified: 2023-05-14 13:29 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
.Added support for the cloned MAC address Cloned MAC address is the MAC address of the device WAN port which is the same as the MAC address of the machine. With this update, users can specify the bonding or bridge interface with the MAC address or the strategy such as `random` or `preserve` to get the default MAC address for the bonding or bridge interface.
Clone Of: 2143458
Environment:
Last Closed: 2023-05-09 07:38:23 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github linux-system-roles network pull 525 0 None open adding cloned_mac 2022-11-17 21:49:00 UTC
Red Hat Issue Tracker RHELPLAN-139856 0 None None None 2022-11-17 19:22:02 UTC
Red Hat Product Errata RHEA-2023:2246 0 None None None 2023-05-09 07:38:47 UTC

Description Wen Liang 2022-11-17 19:17:29 UTC 
+++ This bug was initially created as a clone of Bug #2143458 +++

Description of problem:

The users want to create the bonding interface with the MAC address
specified by themselves or specify the strategy (e.g. random, preserve)
to get the default MAC for the bonding interface. Thus, add support for
the cloned MAC address.
Comment 7 Jon Trossbach 2022-12-19 14:57:06 UTC 
@djez 
@rmeggins

Same problem as https://bugzilla.redhat.com/show_bug.cgi?id=2129620
Comment 8 Jon Trossbach 2023-01-13 13:18:10 UTC 
For this will be testing network/tests_bond_cloned_mac_initscripts.yml tests_bond_cloned_mac_nm.yml and network/tests_bridge_cloned_mac_initscripts.yml tests_bridge_cloned_mac_nm.yml unless I hear otherwise
Comment 9 Jon Trossbach 2023-01-13 22:12:05 UTC 
tests_bond_cloned_mac_initscripts.yml tests_bond_cloned_mac_nm.yml and tests_bridge_cloned_mac_initscripts.yml tests_bridge_cloned_mac_nm.yml

tests_bond_cloned_mac_initscripts.yml
:: [ 16:28:13 ] :: [   FAIL   ] :: Test network with ANSIBLE-2 against RHEL_6_10_GA (Expected 0, got 1)
:: [ 16:28:12 ] :: [   FAIL   ] :: Test tests_bond_cloned_mac_initscripts.yml (Assert: expected 0, got 2)
:: [ 16:29:26 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_7_9_GA (Expected 0, got 0)
:: [ 16:29:25 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:31:07 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_7_0_GA (Expected 0, got 0)
:: [ 16:31:06 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:32:57 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_8_TESTING (Expected 0, got 0)
:: [ 16:32:56 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:33:36 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_1_0_GA (Expected 0, got 0)
:: [ 16:33:35 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:34:20 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_2_TESTING (Expected 0, got 0)
:: [ 16:34:19 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_initscripts.yml (Assert: expected 0, got 0)

tests_bond_cloned_mac_nm.yml
:: [ 16:40:28 ] :: [   FAIL   ] :: Test network with ANSIBLE-2 against RHEL_6_10_GA (Expected 0, got 1)
:: [ 16:40:27 ] :: [   FAIL   ] :: Test tests_bond_cloned_mac_nm.yml (Assert: expected 0, got 2)
:: [ 16:41:35 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_7_9_GA (Expected 0, got 0)
:: [ 16:41:34 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 16:43:02 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_7_0_GA (Expected 0, got 0)
:: [ 16:43:01 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 16:44:31 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_8_TESTING (Expected 0, got 0)
:: [ 16:44:30 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 16:45:34 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_1_0_GA (Expected 0, got 0)
:: [ 16:45:33 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 16:46:39 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_2_TESTING (Expected 0, got 0)
:: [ 16:46:38 ] :: [   PASS   ] :: Test tests_bond_cloned_mac_nm.yml (Assert: expected 0, got 0)

tests_bridge_cloned_mac_initscripts.yml
:: [ 16:53:56 ] :: [   FAIL   ] :: Test network with ANSIBLE-2 against RHEL_6_10_GA (Expected 0, got 1)
:: [ 16:53:55 ] :: [   FAIL   ] :: Test tests_bridge_cloned_mac_initscripts.yml (Assert: expected 0, got 2)
:: [ 16:55:13 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_7_9_GA (Expected 0, got 0)
:: [ 16:55:12 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:56:51 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_7_0_GA (Expected 0, got 0)
:: [ 16:56:50 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:58:22 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_8_TESTING (Expected 0, got 0)
:: [ 16:58:21 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:59:02 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_1_0_GA (Expected 0, got 0)
:: [ 16:59:01 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_initscripts.yml (Assert: expected 0, got 0)
:: [ 16:59:43 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_2_TESTING (Expected 0, got 0)
:: [ 16:59:42 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_initscripts.yml (Assert: expected 0, got 0)

tests_bridge_cloned_mac_nm.yml
:: [ 17:03:48 ] :: [   FAIL   ] :: Test network with ANSIBLE-2 against RHEL_6_10_GA (Expected 0, got 1)
:: [ 17:03:47 ] :: [   FAIL   ] :: Test tests_bridge_cloned_mac_nm.yml (Assert: expected 0, got 2)
:: [ 17:04:55 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_7_9_GA (Expected 0, got 0)
:: [ 17:04:54 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 17:06:15 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_7_0_GA (Expected 0, got 0)
:: [ 17:06:14 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 17:07:28 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_8_8_TESTING (Expected 0, got 0)
:: [ 17:07:26 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 17:08:32 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_1_0_GA (Expected 0, got 0)
:: [ 17:08:31 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_nm.yml (Assert: expected 0, got 0)
:: [ 17:09:41 ] :: [   PASS   ] :: Test network with ANSIBLE-2 against RHEL_9_2_TESTING (Expected 0, got 0)
:: [ 17:09:40 ] :: [   PASS   ] :: Test tests_bridge_cloned_mac_nm.yml (Assert: expected 0, got 0)

[root@netqe4 Upstream-testsuite]# uname -r
5.14.0-230.el9.x86_64
[root@netqe4 Upstream-testsuite]# rpm -q rhel-system-roles
rhel-system-roles-1.21.0-0.14.el9.noarch
Comment 13 errata-xmlrpc 2023-05-09 07:38: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 (rhel-system-roles 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-2023:2246
Note You need to log in before you can comment on or make changes to this bug.