[ovs-discuss] Bridge datapath_type gets reset after couple of reboots

[Alex Yeh (ayeh)]

Ben,
	Yes, it is intentional, ayeh-br1 has netdev set.

Thanks
Alex
(\__/)
(='.'=) 
(")_(")

-----Original Message-----
From: Ben Pfaff <blp at ovn.org> 
Sent: Thursday, June 20, 2019 5:29 PM
To: Alex Yeh (ayeh) <ayeh at cisco.com>
Cc: Shriroop Joshi (shrirjos) <shrirjos at cisco.com>; ovs-discuss at openvswitch.org; Tobias Hofmann -T (tohofman - AAP3 INC at Cisco) <tohofman at cisco.com>
Subject: Re: [ovs-discuss] Bridge datapath_type gets reset after couple of reboots

The ovsdb-tool.log shows several bridges being inserted but only one of them has its datapath_type set to netdev.  Is that intentional?

On Thu, Jun 20, 2019 at 11:46:09PM +0000, Alex Yeh (ayeh) wrote:
> Hi Ben,
> 	Thanks for your reply and the suggestion.
> 	We looked at the output of the command and don't seen command explicitly modified the datapath_type on ayeh-br1 bridge. I turned on the debug on ovs-vswitchd for the reboot hopefully it can provide some information. I'm attaching the output from the command and the debug log from ovs-vswitchd. 
> 
> Thanks much for any tip anyone can spare, Alex
> (\__/)
> (='.'=)
> (")_(")
> 
> -----Original Message-----
> From: Ben Pfaff <blp at ovn.org>
> Sent: Thursday, June 20, 2019 9:26 AM
> To: Shriroop Joshi (shrirjos) <shrirjos at cisco.com>
> Cc: ovs-discuss at openvswitch.org; Alex Yeh (ayeh) <ayeh at cisco.com>; 
> Tobias Hofmann -T (tohofman - AAP3 INC at Cisco) <tohofman at cisco.com>
> Subject: Re: [ovs-discuss] Bridge datapath_type gets reset after 
> couple of reboots
> 
> On Thu, Jun 20, 2019 at 12:34:31AM +0000, Shriroop Joshi (shrirjos) via discuss wrote:
> > I encountered a strange problem with OVS-DPDK. I created a bridge and changed its datapath_type to netdev after initializing DPDK.
> > After a couple of reboots, it's datapath_type gets reset with DPDK initialized. Also, vnics connected to the bridge get disconnected. We don't have any interfaces connected to the bridge. 
> 
> It's usually possible to track down the cause of database changes with "ovsdb-tool -mm show-log", which shows what program made a change and when and sometimes additional comments.