[ovs-discuss] controller's role mismatch?

Fri Apr 22 09:32:26 UTC 2016

Hello,

I had to use 2 switches/bridges to reproduce the problem. Logs in attachments.

Just for the time orientation:
Enabling 2 masters for 2 switches (controller firstly sent slave automatically, and when it finds out that it is the first connection from that device, it sends master then)

2016-04-22T08:48:53.341Z|00080|vconn|DBG|tcp:10.25.2.14:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x0): role=nochange
2016-04-22T08:48:53.341Z|00081|vconn|DBG|tcp:10.25.2.14:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x0): role=equal
2016-04-22T08:48:53.343Z|00082|vconn|DBG|tcp:10.25.2.14:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x1): role=slave generation_id=0
2016-04-22T08:48:53.343Z|00083|vconn|DBG|tcp:10.25.2.14:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x1): role=slave generation_id=0
2016-04-22T08:48:53.465Z|00095|vconn|DBG|tcp:10.25.2.13:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x0): role=nochange
2016-04-22T08:48:53.465Z|00096|vconn|DBG|tcp:10.25.2.13:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x0): role=equal
2016-04-22T08:48:53.467Z|00097|vconn|DBG|tcp:10.25.2.13:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x1): role=slave generation_id=0
2016-04-22T08:48:53.467Z|00098|vconn|DBG|tcp:10.25.2.13:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x1): role=slave generation_id=0
2016-04-22T08:48:53.501Z|00099|vconn|DBG|tcp:10.25.2.14:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x2): role=nochange
2016-04-22T08:48:53.501Z|00100|vconn|DBG|tcp:10.25.2.14:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x2): role=slave generation_id=0
2016-04-22T08:48:53.503Z|00101|vconn|DBG|tcp:10.25.2.14:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x3): role=master generation_id=1
2016-04-22T08:48:53.503Z|00102|vconn|DBG|tcp:10.25.2.14:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x3): role=master generation_id=1
2016-04-22T08:48:54.121Z|00142|vconn|DBG|tcp:10.25.2.13:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x3): role=nochange
2016-04-22T08:48:54.121Z|00143|vconn|DBG|tcp:10.25.2.13:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x3): role=slave generation_id=0
2016-04-22T08:48:54.122Z|00144|vconn|DBG|tcp:10.25.2.13:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x4): role=master generation_id=1
2016-04-22T08:48:54.123Z|00145|vconn|DBG|tcp:10.25.2.13:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x4): role=master generation_id=1

Enabling the rest 4 slaves  (2 slaves each switch)
2016-04-22T08:48:56.718Z|00194|vconn|DBG|tcp:10.25.2.12:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x0): role=nochange
2016-04-22T08:48:56.718Z|00195|vconn|DBG|tcp:10.25.2.12:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x0): role=equal generation_id=1
2016-04-22T08:48:56.721Z|00196|vconn|DBG|tcp:10.25.2.12:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x1): role=slave generation_id=2
2016-04-22T08:48:56.721Z|00197|vconn|DBG|tcp:10.25.2.12:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x1): role=slave generation_id=2
2016-04-22T08:48:56.877Z|00209|vconn|DBG|tcp:10.25.2.13:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x0): role=nochange
2016-04-22T08:48:56.877Z|00210|vconn|DBG|tcp:10.25.2.13:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x0): role=equal generation_id=2
2016-04-22T08:48:56.879Z|00211|vconn|DBG|tcp:10.25.2.13:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x1): role=slave generation_id=3
2016-04-22T08:48:56.879Z|00212|vconn|DBG|tcp:10.25.2.13:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x1): role=slave generation_id=3
2016-04-22T08:48:57.054Z|00224|vconn|DBG|tcp:10.25.2.12:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x0): role=nochange
2016-04-22T08:48:57.054Z|00225|vconn|DBG|tcp:10.25.2.12:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x0): role=equal generation_id=1
2016-04-22T08:48:57.055Z|00226|vconn|DBG|tcp:10.25.2.12:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x1): role=slave generation_id=2
2016-04-22T08:48:57.055Z|00227|vconn|DBG|tcp:10.25.2.12:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x1): role=slave generation_id=2
2016-04-22T08:48:57.207Z|00239|vconn|DBG|tcp:10.25.2.14:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x0): role=nochange
2016-04-22T08:48:57.207Z|00240|vconn|DBG|tcp:10.25.2.14:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x0): role=equal generation_id=2
2016-04-22T08:48:57.209Z|00241|vconn|DBG|tcp:10.25.2.14:6653: received: OFPT_ROLE_REQUEST (OF1.3) (xid=0x1): role=slave generation_id=3
2016-04-22T08:48:57.209Z|00242|vconn|DBG|tcp:10.25.2.14:6653: sent (Success): OFPT_ROLE_REPLY (OF1.3) (xid=0x1): role=slave generation_id=3

Peter Gubka

-----Original Message-----
From: Ben Pfaff [mailto:blp at ovn.org] 
Sent: Thursday, April 21, 2016 6:56 PM
To: Peter Gubka -X (pgubka - PANTHEON TECHNOLOGIES at Cisco) <pgubka at cisco.com>
Cc: bugs at openvswitch.org
Subject: Re: [ovs-discuss] controller's role mismatch?

On Thu, Apr 21, 2016 at 02:55:46PM +0000, Peter Gubka -X (pgubka - PANTHEON TECHNOLOGIES at Cisco) wrote:
> Is something wrong with my approach or is it a bug in openvswitch?
> Is role parameter reliable?

Please enable OpenFlow debug logging with "-vvconn" or "ovs-appctl vlog/set vconn", then reproduce the problem, then send us the ovs-vswitchd log.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ovs-commands-and-db-list.txt
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160422/326164e4/attachment-0002.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ovs-vswitchd.log
Type: application/octet-stream
Size: 56479 bytes
Desc: ovs-vswitchd.log
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20160422/326164e4/attachment-0002.obj>