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.

Created attachment 1243584 [details]
messages log

Description of problem:
- ifup of an interface that is already a member of a slave should fail, but claims to succeed.

If we have an interface that is already a member of a slave bridge and we removed this bridge and added another bridge on top of him. When we issue ifup to this interface, we get:
"device ens1f0 is already a member of a bridge; can't enslave it to bridge n11"
[root@orchid-vds1 ~]# echo $?
0

But such operation should have been failed. 
 

Version-Release number of selected component (if applicable):
3.10.0-514.6.1.el7.x86_64
initscripts-9.49.37-1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Create bridge n11 over ens1f0 using ifcfg-* 

brctl show 
n11             8000.0015173dcdaa       no              ens1f0

2. Delete this bridge n11 manually from the host
3. Create another bridge net1 and addif on top ens1f0 manually on the host
4. Run ifup ens1f0 

Actual results:
device ens1f0 is already a member of a bridge; can't enslave it to bridge n11.
[root@orchid-vds1 ~]# echo $?
0

Expected results:
We should fail and get a nice error.

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.