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:
When booting with "bridge=br0:ens2,ens3 vlan=vlan5:br0", interface vlan5 does not receive IPv4 address via DHCP.

Version-Release number of selected component (if applicable):
NetworkManager-1.26.0-7.el8
dracut-049-95.git20200804.el8.x86_64

How reproducible:
always

Steps to Reproduce:
1. boot with "bridge=br0:ens2,ens3 vlan=vlan5:br0"

Actual results:
DHCP request is visible on the server, but for different MAC address (MAC of vlan5 happens to be the same as MAC of br0, DHCP request is for some random MAC, which even changes, when trying for longer time), vlan5 does not receive the IPv4 address.

Expected results:
There is no MAC mismatch, and vlan5 receives IPv4 address.

Additional info:
This bug is reproducible within NetworkManager-ci, it was discovered during implementation of initramfs (dracut) tests for NetworkManager.

Hi Filip,

this sounds like https://bugzilla.redhat.com/show_bug.cgi?id=1818697 which has been fixed in NetworkManager-1.28.0-0.1.el8, can you try to reproduce it against that version?

Thanks,
Antonio

Hi Antonio,

in NetworkManager-1.28.0-0.1.el8 problem seems to be gone, the MAC address of the first device in bridge is seen by DHCP server, and so lease is renewed correctly. Will this be backported to 1-26 branch?

I will update NetworkManager-ci, when we make the test stable enough.

Thanks,
Filip

Hi Filip,

glad that it's been fixed already ;)

I'm closing this, anyone can open a zstream request if this needs backporting.

Thanks,
Antonio

*** This bug has been marked as a duplicate of bug 1818697 ***