Bug 1478675

Summary:	NetworkManager 1.8.2 GUI lacks team creation/management options
Product:	[Fedora] Fedora	Reporter:	Dmitry Burstein <dmitryburstein>
Component:	control-center	Assignee:	Control Center Maintainer <control-center-maint>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	26	CC:	bgalvani, control-center-maint, dcbw, fgiudici, fmuellner, lkundrak, mkasik, ofourdan, redhat, rstrode, tiagomatos
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 12:54:36 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:

Description Dmitry Burstein 2017-08-06 01:07:54 UTC

Description of problem:
In this version of NetworkManager (as opposed to the previous one) it is impossible to create or manage team interfaces in the GUI tool, nmcli being the only option.

Version-Release number of selected component (if applicable):
1.8.2

How reproducible:
Every time

Steps to Reproduce:
1.Press the Super key to enter the Activities Overview, type 'control network' and then press Enter.
2.Click the plus symbol to open the selection list.
3.

Actual results:
There is no team (or bond for this matter) option in the list.

Expected results:
'Team' among the other options.

Additional info:
I do have the team plugin installed, and can create/manage the interface through the nmcli.

Comment 1 Beniamino Galvani 2017-08-07 16:28:08 UTC

I'm reassigning this to the proper component, gnome-control-center.

Note that you can also configure most of the connection types supported by NetworkManager through the nm-connection-editor tool.

Comment 2 Stephen Satchell 2018-01-26 20:52:30 UTC

If removing "all that enterprise stuff" was intentional, then the documentation needs to be updated to remove the instructions for using the Gnome NetworkManager interface.

Comment 3 Fedora End Of Life 2018-05-03 08:36:54 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2018-05-29 12:54:36 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.