Bug 1310461 - duplicated team device
Summary: duplicated team device
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: control-center
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Bastien Nocera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-21 21:10 UTC by Vladimir Benes
Modified: 2016-04-29 12:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-29 12:24:43 UTC
Target Upstream Version:


Attachments (Terms of Use)
screenshot (218.71 KB, image/png)
2016-02-21 21:12 UTC, Vladimir Benes
no flags Details

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.


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