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:
network scripts: don't print an error if slave device is already enslaved in the correct bridge

Version-Release number of selected component (if applicable):
initscripts-9.03.38-1.el6.x86_64

How reproducible:


Steps to Reproduce:
1. service NetworkManager stop ; service network stop
2. configure a bridge br0 with ONBOOT=yes and enslaved physical device eth0
3. service network start
4. service network restart
  
Actual results:
in the middle of restart, this message is printed:
> eth0:  device eth0 is already a member of a bridge; can't enslave it to bridge br0.

Expected results:
network-scripts can see that eth0 is correctly enslaved to br0 so there is no need to print the error

Additional info:

Hi,

I followed your steps to reproduce on clean install of RHEL 6.4 and 6.3 but this error never occured. Can you provide your ifcfg scripts?

Command "service network restart" performs "network stop" and "network start". After "network stop" br0 is removed, so eth0 cannot be already enslaved on the start call.

Hi, I hit the behaviour when I was testing bridges in NM so the problem may have been caused by some NM/network-scripts interference as I didn't hit it after on machines using just one or the other exclusively, so I'm closing the bug.