Bug 1310461

Summary: duplicated team device
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: control-centerAssignee: Bastien Nocera <bnocera>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 7.3CC: thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-29 12:24:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot none

Description Vladimir Benes 2016-02-21 21:10:55 UTC 
Description of problem:
when team device is created there are two different devices in control-center's Network overview. One with arrows (which is in my opinion incorrect and cannot be deleted via -) and the other one with the same icon as bond (this one can be deleted via -).
 
Version-Release number of selected component (if applicable):
NetworkManager-1.0.6-27.el7.x86_64
control-center-3.14.5-8.el7.x86_64

How reproducible:
always

Steps to Reproduce:
1.go to control-center create a team device with 1.2.3.4/24 address
2.assign a team slave into it
3.save both

Actual results:
two devices (see attachment)

Expected results:
one device

Additional info:
Comment 1 Vladimir Benes 2016-02-21 21:12:03 UTC 
Created attachment 1129103 [details]
screenshot
Comment 2 Thomas Haller 2016-02-22 12:46:07 UTC 
Could be a dupe of bug 1294728
Comment 3 Bastien Nocera 2016-04-29 12:24:43 UTC 
Support for enterprise networking features will be removed in future versions of GNOME and of RHEL 7.x. We advise that you test Cockpit instead, which is better suited to manipulate enterprise networking feature.

Teaming support for Cockpit is tracked at:
https://github.com/cockpit-project/cockpit/issues/4330

Bonding, bridging and VLAN support are already implemented.