Bug 1437598
| Summary: | After down the bridge, it's not possible start bridge + slaves at once | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Waldirio M Pinheiro <wpinheir> | ||||||
| Component: | NetworkManager | Assignee: | Beniamino Galvani <bgalvani> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 7.3 | CC: | aloughla, atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller, vbenes | ||||||
| Target Milestone: | rc | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | All | ||||||||
| OS: | All | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-04-10 13:22:08 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1470965 | ||||||||
| Attachments: |
|
||||||||
|
Description
Waldirio M Pinheiro
2017-03-30 15:45:13 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. Created attachment 1350463 [details]
[PATCH 1/2] device: make nm_device_state_reason_to_str() public
Created attachment 1350464 [details]
[PATCH 2/2] core: allow slaves to autoactivate when master is available
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. lgtm Applied to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b31118cfd2ce863d4c4808a9d410f03be6d9170e and nm-1-10: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-10&id=8db21209798806bca583e4e9be2d25a252c29583 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 |