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 bond is created with slaves these slaves are not upped. No other way how to up them. This looks like a regression to 7.1.
There is no other way how to up them in control-center or in other gui application.
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.open control-center network
2.click plus and select bond
3.set ipv4 to manual and set ip
4.set ipv6 to ignore
5.add slave to ethernet device
6.save bond
Actual results:
bond connected but slave is not
Expected results:
both should be connected
Additional info:
reopening just for reconsidering the situation when
1. the device for bond slave was disconnected by nmcli device disconnect
2. the device is not grabbed by NM's autoconnect anymore as it's marked unsuitable for this because of device disconnect
3. do we want to connect it when the bond is created with slave profile?
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.