Bug 1075198 - nm-connection-editor: allow to create bond/team/bridge without any ports/slaves
Summary: nm-connection-editor: allow to create bond/team/bridge without any ports/slaves
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: network-manager-applet
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Jirka Klimes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1113520
TreeView+ depends on / blocked
 
Reported: 2014-03-11 16:58 UTC by Jiri Pirko
Modified: 2015-05-05 01:25 UTC (History)
6 users (show)

Fixed In Version: network-manager-applet-0.9.11.0-1.git20141119.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 13:35:43 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0596 0 normal SHIPPED_LIVE network-manager-applet bug fix and enhancement update 2015-03-05 17:21:27 UTC

Description Jiri Pirko 2014-03-11 16:58:41 UTC 
Currently, there is not possible to create bond/team/bridge without any slave/port connection in it. nmcli allows to do it. There is no reason why this should not be possible in nm-connection-editor.
Comment 1 Jirka Klimes 2014-03-19 09:52:31 UTC 
Bridge connections can be created without slaves in nm-connection-editor.

The code allowing that also for bond and team is available in upstream branch
jk/rh1075198-editor-team-bond  (network-manager-applet repository)
Comment 2 Dan Williams 2014-03-20 23:42:30 UTC 
I agree that bond/team should be able to be created without slaves and that bridge/bond/team should be consistent with each other.

Patch looks good to me.
Comment 3 Jirka Klimes 2014-03-21 07:59:31 UTC 
Upstream master commit:
8a5e838 editor: allow creating bond/team connections without slaves (rh #1075198)
Comment 8 errata-xmlrpc 2015-03-05 13:35:43 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0596.html
Note You need to log in before you can comment on or make changes to this bug.