Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1415695 - ifup of an interface that is already a member of a slave should fail, but claims to succeed
Summary: ifup of an interface that is already a member of a slave should fail, but cla...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Lukáš Nykrýn
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1549689
TreeView+ depends on / blocked
 
Reported: 2017-01-23 13:09 UTC by Michael Burman
Modified: 2021-01-15 07:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:31:04 UTC
Target Upstream Version:


Attachments (Terms of Use)
messages log (156.75 KB, application/x-gzip)
2017-01-23 13:09 UTC, Michael Burman
no flags Details

Description Michael Burman 2017-01-23 13:09:27 UTC
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.

Comment 7 RHEL Program Management 2021-01-15 07:31:04 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.