Bug 1369215 - bridge not started automatically
Summary: bridge not started automatically
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-22 17:00 UTC by Subhendu Ghosh
Modified: 2017-02-28 10:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-28 10:29:45 UTC
Type: Bug
thaller: needinfo-

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Subhendu Ghosh 2016-08-22 17:00:30 UTC 
Description of problem:

NetworkManager does not automatically start up bridges interfaces and related slaves even when marked to do so in the GUI

Version-Release number of selected component (if applicable):
NetworkManager-1.2.2-2.fc24.x86_64


How reproducible:
Always

Steps to Reproduce:
1. create a bridge with a single hardware interface as a slave.
2. mark the bridge to autostart + available to all
3. mark slave to autostart + available to all

Actual results:

bridge not started
slave not connected

Expected results:

bridge and slave should be connected.

Additional info:
Comment 1 Dan Williams 2016-08-22 19:12:12 UTC 
Can you:

sudo nmcli g log level debug

and then reproduce the issue, then:

sudo journalctl -b -u NetworkManager

and attach as a private attachment?  To return debug logging to normal:

sudo nmcli g log level info
Comment 2 Fedora End Of Life 2017-02-28 10:08:24 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 26 development cycle.
Changing version to '26'.
Comment 3 Thomas Haller 2017-02-28 10:29:45 UTC 
Closing as incomplete.

If the issue still exists or more information can be provided, please reopen.

thanks!
Note You need to log in before you can comment on or make changes to this bug.