Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
When I use gnome-control-center, I create bridge device with a port. After that the master connection is upped by itself, slave (port) connection however is not upped. There is now way to up it using gnome-control-center.
Version-Release number of selected component (if applicable):
control-center-3.8.6-13.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1. create bridge with one port using gnome-control-center
Actual results:
port connection is not upped and there is not way to do it by gnome-control-center
Expected results:
there is a possibility to up the device by gnome-control-center. Also the port should be probably upped, so as the bridge master is after it is created.
Additional info:
none
Matthias, from my pov this is a bug not RFE. User that uses only gnome-control-center is not able to get a bridge into function (note this applies to team and bonding as well). He has to use a different tool for it. So therefore, in fact, gnome-control-center is unusable to manage bridge, bonding, team devices.
We also need to see those ports profiles under wired sections and possibility to activate them via double click. Until then virtual networking in anaconda GUI is completely useless.
Matthias, no design work is needed. The UI already works when the slave device is active. Make the connection ("profile") available to choose when it is not active and you're done.
(In reply to David Jaša from comment #5)
> Matthias, no design work is needed. The UI already works when the slave
> device is active. Make the connection ("profile") available to choose when
> it is not active and you're done.
Advanced network configuration in GNOME's Settings are informational only. It's certainly useful for those settings to be visible when used, but adding configuration for those types of network configurations in the Network panel is clearly out of scope.
Comment 8RHEL Program Management
2014-06-16 15:36:29 UTC
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.
(In reply to Bastien Nocera from comment #7)
> (In reply to David Jaša from comment #5)
> > Matthias, no design work is needed. The UI already works when the slave
> > device is active. Make the connection ("profile") available to choose when
> > it is not active and you're done.
>
> Advanced network configuration in GNOME's Settings are informational only.
> It's certainly useful for those settings to be visible when used, but adding
> configuration for those types of network configurations in the Network panel
> is clearly out of scope.
Sorry, but I do not understand your statement. "GNOME's Settings" are not informational only. Using that interface, you can setup many devices including bridge, bonding, team and more. The functionality is quite complete.
This bugzilla is about as simple thing as adding a toggle to up/down some device. From my perspective, it is near trivial to do it. After that, the tool would be "complete".
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.