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:
Can't initiate two bridge adapters on boot.
How reproducible:
100%
Steps to Reproduce:
I use diskless boot via iSCSI and multipath. Dracut takes params from grub2:
iscsi_initiator=iqn.2001-01.local.domain:node1 netroot=iscsi:@10.0.0.2::3260::iqn.2001-01.local.domain:iscsitest.lv_node1 netroot=iscsi:@192.92.92.108::3260::iqn.2001-01.local.domain:iscsitest.lv_node1 ifname=enp2s0:10:fe:ed:03:aa:51 ifname=enp4s0:f4:6d:04:e6:78:80 ip=enp2s0:dhcp ip=enp4s0:dhcp
Both adapters acquire their addresses, then make connection to iSCSI target by two distinct IP, mutlipath makes a dev.
Now I'm trying to make bridges on this adapters, for VMs. Used dracut params:
iscsi_initiator=iqn.2001-01.local.domain:node1 netroot=iscsi:@10.0.0.2::3260::iqn.2001-01.local.domain:iscsitest.lv_node1 netroot=iscsi:@192.92.92.108::3260::iqn.2001-01.local.domain:iscsitest.lv_node1 ifname=enp2s0:10:fe:ed:03:aa:51 ifname=enp4s0:f4:6d:04:e6:78:80 bridge=br0:enp2s0 bridge=br1:enp4s0 ip=br0:dhcp ip=br1:dhcp
But only one bridge activates (enp2s0 at my case, first one in alphabetical order), then iSCSI connection crashes, because second adapter is inactive and cannot reach required network.
Why can't I have two bridges on boot?
Can you boot with "rd.debug" on the kernel command line and attach /run/initramfs/rdsosreport.txt ??
Also why "Version: 7.3" ?
Which version of dracut? Which version of RHEL?
Message about alphabetical order was incorrect, the only starting bridge is the last one in kernel params, in case of this:
bridge=br1:enp2s0 ip=br1:dhcp bridge=br0:enp4s0 ip=br0:dhcp
only br0 starts succesfully. Adding "bootdev=br1" doesn't fix it.
There's no rdsosreport.txt after adding "rd.debug", but "messages" got additional info.
According to logs, br1 (first one in kernel commandline) doesn't initiate at all.
dracut Version: 033-161.el7_0.173
/etc/redhat-release
CentOS Linux release 7.0.1406 (Core)
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://rhn.redhat.com/errata/RHBA-2016-2530.html