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.
If we create ethernet setting at the beginning, we must specify the MAC address for the virtual interface which we cannot know that
before the virtual interface been created in kernel. So in this case, we need generate that MAC address and hoping it does not overlap.
And meanwhile, we have important use case in RHV, which need the bridge to use the MAC address of first attached ethernet.
If we specified the MAC address initially, we lose the support of that use case.
The concern of reapply should be fixed by https://bugzilla.redhat.com/show_bug.cgi?id=1786547 at NetworkManager site.
I will try to beg NetworkManager to bring fix to nmstate issue.
nmstate-0.2.10-1.el8.noarch
NetworkManager-1.22.8-4.el8.x86_64
DISTRO=RHEL-8.2.1-20200521.n.0
Linux hp-dl388g8-08.rhts.eng.pek2.redhat.com 4.18.0-193.4.1.el8_2.x86_64 #1 SMP Fri May 15 15:02:51 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
1. Create a bridge with slave
2. Add a new slave --- reapply ok
3. Change mtu --- link gets down/up. Like before, no ethernet settings. Track on https://bugzilla.redhat.com/show_bug.cgi?id=1786547
If in step 1, you specify an ethernet setting like mtu or mac, then the step 3 will work.
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, 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:3052