NetworkManager control of bridges

[Paul Knox-Kennedy]

> -----Original Message-----
> From: users-bounces at lists.fedoraproject.org 
> [mailto:users-bounces at lists.fedoraproject.org] On Behalf Of poma
> Sent: 14 February 2014 09:04
> To: Community support for Fedora users
> Subject: Re: NetworkManager control of bridges
> 
> On 14.02.2014 09:52, Paul Knox-Kennedy wrote:
> > Since F20 Beta, I have been running my bridge under NM 
> control without 
> > too much trauma, but on Tuesday, it stopped working. A few 
> other users 
> > seemed to have an issue at the same time, and resolved it 
> by deleting 
> > all NM connections and re-adding them. This is still not 
> working for me.
> >  
> > At the moment, NM fails to bring up my network on boot every time.
> > However, if I log in as root and run systemctl restart 
> NetworkManager, 
> > everything comes up correctly.
> >  
> > I have pasted the output of systemctl status NetworkManager 
> after the 
> > reboot, and after the restart here: http://ur1.ca/gmj61. At 
> line 48, 
> > the bridge fails due to a timeout on reboot. On the nm restart, 
> > everything comes up cleanly.
> >  
> > Can anyone tell me where to look next?
> >  
> > Thanks
> > Paul
> 
> "configured bridge fails to start properly"
> https://bugzilla.redhat.com/show_bug.cgi?id=1063290
> 
> 
> poma
> 
> 

Thanks! This has been driving me slightly mad all week. Yum downgrade 
of libnl3 and libnl3-cli to 3.2.21, and the addition of
yum-plugin-versionlock,
and I now have a working system.

Cheers
Paul



NOTICE & DISCLAIMER 
This email including attachments (this "Document") is confidential and may contain legally privileged information.  If you have received this Document in error please notify the sender immediately and delete this Document from your system without using, copying, disclosing or disseminating it or placing any reliance upon its contents.  We cannot accept liability for any breaches of confidence arising through use of this Document.

The information contained in this Document is provided solely for information purposes on an "as is" basis without warranty of any kind, either express or implied, including without limitation any implied warranty of satisfactory or merchantable quality, fitness for a particular purpose or freedom from error or infringement.  The user relies on the information contained herein, and its accuracy or otherwise, entirely at their own risk.

Any opinions expressed in this Document are those of the author and do not necessarily reflect the opinions of Telsis.  We will not accept responsibility for any commitments made by our employees outside the scope of our business.