Thanks very much for your replies to my issue, folks.

I’ve decide to remove OVS from the system and return to Linux bridging. OVS is 
the only thing that didn’t survive the upgrade to Ubuntu 16.04
and it may take some time to debug the problem, especially with no support from 
Ubuntu. I don’t have that time to spare.

Again, I’m much obliged for your responses.

Regards,

Chad Willman

From: Chad Willman <[email protected]>
Date: Thursday, August 24, 2017 at 7:20 AM
To: "O'Reilly, Darragh" <[email protected]>, Ben Warren 
<[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: Re: [ovs-discuss] problem with openvswitch 2.5.2 after upgrade to 
Ubuntu 16.04

Couple of notes.

I disabled NetworkManager service. It got rid of the NetworkManager kern.log, 
but the “device ovsbr0 entered/left promiscuous mode” is still there.

Regarding creating the bridge using ovs-vsctl vs brctl, I completely removed 
the ovsbr0 bridge, removed the openvswitch 2.5.2 packages, and verified
that “brctl show” displayed nothing. Then I reinstalled the openvswitch 2.5.2 
packages and recreated the ovsbr0 bridge using ovs-vsctl.
The “brctl show” command still displays the ovsbr0 bridge, even though it was 
created with the ovs-vsctl command (re: Ben’s comment earlier in the thread).

Still getting “2017-08-24T12:11:39.089Z|385668|bridge|INFO|bridge ovsbr0: added 
interface ovsbr0 on port 65534” in the ovs-vswitchd log as well.

But disabling the NetworkManager service was a clue. The Ubuntu system I’m 
trying to fix is a hybrid of sorts. It was installed with Ubuntu Server 14.04,
but was later modified to enable graphical access through VNC (hence, 
NetworkManager being active).  It’s possible there are other elements at work,
that are related to that hybrid configuration.

The interesting part is that the system has been operating fine with 14.04 for 
3 years. It wasn’t until the upgrade to Ubuntu 16.04 that the issue began.
That upgrade took openvswitch from 2.0.2 to 2.5.2 (Ubuntu’s package versions).

Thanks for the responses.

CW

From: "O'Reilly, Darragh" <[email protected]>
Date: Thursday, August 24, 2017 at 2:54 AM
To: Chad Willman <[email protected]>, Ben Warren <[email protected]>
Cc: "[email protected]" <[email protected]>
Subject: RE: [ovs-discuss] problem with openvswitch 2.5.2 after upgrade to 
Ubuntu 16.04


Maybe a NetworkManager problem. I would disable it completely on a server, but 
maybe you could change it to ignore OVS interfaces.

From: [email protected] 
[mailto:[email protected]] On Behalf Of Chad Willman
Sent: 23 August 2017 18:20
To: Ben Warren <[email protected]>
Cc: [email protected]
Subject: Re: [ovs-discuss] problem with openvswitch 2.5.2 after upgrade to 
Ubuntu 16.04

Hi,

I eliminated the lxcbr0, but still have the same problem with ovs-vswitchd 
eating CPU.


cwillman@harley:~$ sudo brctl show

bridge name

bridge id STP enabled

interfaces

ovsbr0

8000.c6074be69e43  no em1

vnet0

vnet1

vnet2





kern.log is also flooding with this message - Aug 23 07:36:03 harley 
NetworkManager[2481]: <info>  [1503491763.8976] device (ovsbr0): enslaved to 
non-master-type device ovs-system; ignoring

Aug 23 07:36:03 harley kernel: [58455.254778] device ovsbr0 entered promiscuous 
mode

Aug 23 07:36:03 harley kernel: [58455.257975] device ovsbr0 left promiscuous 
mode





Would appreciate any other suggestions.





Regards,





Chad




From: Chad W <[email protected]<mailto:[email protected]>>
Date: Wednesday, August 23, 2017 at 11:55 AM
To: Ben Warren <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [ovs-discuss] problem with openvswitch 2.5.2 after upgrade to 
Ubuntu 16.04

Hi Ben and thanks for the response.

brctl shows me this -

bridge namebridge id

STP enabledinterfaces

lxcbr08000.00163e000000

no

ovsbr08000.c6074be69e43

no em1

vnet0

vnet1

vnet2





The ovsbr0 bridge looks right, but the lxcbr0 should not be there.

Not sure how it got there (we have multiple admins on this system), but I’ll 
try nuking it.



Regards,



Chad




From: Ben Warren <[email protected]<mailto:[email protected]>>
Date: Wednesday, August 23, 2017 at 11:43 AM
To: Chad W <[email protected]<mailto:[email protected]>>
Cc: "[email protected]<mailto:[email protected]>" 
<[email protected]<mailto:[email protected]>>
Subject: Re: [ovs-discuss] problem with openvswitch 2.5.2 after upgrade to 
Ubuntu 16.04

Hi Chad,

I’ve seen this if regular Linux bridging is enabled.  The command ‘brctl show’ 
will display non-OVS bridges.

regards,
Ben

On Aug 23, 2017, at 9:23 AM, Chad Willman 
<[email protected]<mailto:[email protected]>> wrote:


Is there a forum specific to discing issues encountered ?

My ovs-vswitchd daemon is consuming 400% CPU and flooding ovs-vswitchd.log with 
the same message repeatedly - 
2017-08-23T16:18:28.049Z|641473|bridge|INFO|bridge ovsbr0: added interface 
ovsbr0 on port 65534

Looking for help or ideas for debugging the issue.

Thanks,

CW
_______________________________________________
discuss mailing list
[email protected]<mailto:[email protected]>
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.openvswitch.org%2Fmailman%2Flistinfo%2Fovs-discuss&data=02%7C01%7Ccwillman%40ixiacom.com%7C5dd9d4981a2d4188a8b908d4eac562e8%7C069fd614e3f843728e18cd06724a9b23%7C0%7C0%7C636391580874899442&sdata=4fh3HAzvGF1wT4qTssjqLvoY2S4FiF03c1TIt71rYKw%3D&reserved=0>

_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to