Bug 1065564

Summary: Bridge not activated properly on boot, works when NetworkManager restarted
Product: [Fedora] Fedora Reporter: Robert Hancock <robert.hancock>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: alex, collura, dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-25 17:05:03 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:
Attachments:
Description Flags
journalctl output for NetworkManager from boot and later restart of NetworkManager service none

Description Robert Hancock 2014-02-14 23:39:27 UTC
Created attachment 863522 [details]
journalctl output for NetworkManager from boot and later restart of NetworkManager service

Description of problem:
A bridge has been configured using NetworkManager. When the system boots up, the bridge does not activate fully. In the network settings applet it's shown as Unavailable, and these complaints are seen in the journalctl log:

NetworkManager[1165]: <warn> Failed to activate 'Bridge connection 1': Failed to create virtual interface
<warn> Activation (em1) failed for connection 'bridge0 slave 1'

When I do "service NetworkManager restart", everything seems fine.

Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.0-29.git20140131.fc20.x86_64

How reproducible:
Every time (on this system anyway)

Steps to Reproduce:
1. Create bridge
2. Reboot
3.

Actual results:
Bridge fails to activate

Expected results:
Bridge works properly

Additional info:

Comment 1 Alexander Wigen 2014-02-17 00:27:25 UTC
I'm also hitting this on multiple machines.

Comment 2 Alexander Wigen 2014-02-17 00:52:32 UTC
This is a duplicate of #1063290

Comment 3 Robert Hancock 2014-02-18 16:44:34 UTC
NetworkManager-0.9.9.0-30.git20131003.fc20.x86_64 seems to solve this problem for me.

Comment 4 Robert Hancock 2014-02-25 17:05:03 UTC
Marking as closed as the problem appears to be fixed.