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.
DescriptionWaldirio M Pinheiro
2017-03-30 15:45:13 UTC
Description of problem:
After configure the bridge, when we stop the bridge via cli or UI and just start, the connection didn't come up again.
Version-Release number of selected component (if applicable):
RHEL 7.3
How reproducible:
100%
Steps to Reproduce:
1. down the bridge (nmcli c down BridgeWall)
2. start the bridge (nmcli c up BridgeWall)
3.
Actual results:
Slave still disconnected
Expected results:
Start everything, once I'm using the UI to do this management, I don't have any option to start the slave.
Additional info:
Comment 2Waldirio M Pinheiro
2017-03-30 15:47:18 UTC
Hi
Below some changes that I did on my environment and then the environment is working fine.
---
[root@dvader ~]# nmcli c edit BridgeWall
nmcli> print
nmcli> set connection.autoconnect-slaves 1
nmcli> set bridge.forward-delay 2
nmcli> set bridge.hello-time 1
nmcli> save persistent
nmcli> quit
# nmcli c down BridgeWall
# nmcli c up BridgeWall
---
The most important point here was *set connection.autoconnect-slaves 1* but I believe be one good approach define all values above as default in our RHEL 7.3
Best Regards
--
Waldirio M Pinheiro | Senior Software Maintenance Engineer
Yeah, sadly this is not possible now. In nmcli or nmtui you can up slave to up master too, or as you've pointed out upping master with connection.autoconnect-slaves 1 works as well.
What I see we should have is:
1. possibility to set connection.autoconnect-slaves 1 in nm-connection-editor (and nmtui)
2. possibility to up a connection in nm-connection-editor
(not sure if those RFEs aren't filed already)
There are no options to up bridge slaves in control-center or GNOME Shell and all advanced networking is going to be removed from control-center in the future so we definitely need to add those options to nm-connection-editor for future NM releases.
I think that if the slaves are connection.autoconnect=1 (note: this should be the default, unlike connection.autoconnect-slaves=1 on the master), the slaves should come up automatically.
I need to look into this.
Comment 5Beniamino Galvani
2017-11-10 13:01:05 UTC
Comment 7Beniamino Galvani
2017-11-10 13:04:38 UTC
I think slaves should be able to autoconnect when they have con.autoconnect=yes and the master becomes available, unless the connection/device is blocked because the user explicitly disconnected it.
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://access.redhat.com/errata/RHBA-2018:0778