[OPNFLWPLUG-946] Openflow Connection fails to get estabilished with controller after resync by flapping the ovs interface. Created: 22/Sep/17  Updated: 27/Sep/21  Resolved: 13/Dec/17

Status: Resolved
Project: OpenFlowPlugin
Component/s: openflowplugin-impl, reconciliation-framework
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: A Fathima Thasneem Assignee: Fathima Thasneem
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: File Capture_resync1.pcap     Text File Inventory Config after sync.txt     Text File Inventory Operational after sync.txt     Text File karaf log.txt     Text File ovs-vswitchdlog.txt    
External issue ID: 9199

 Description   

Description :

Openflow Connection fails to get established with controller after flap of ovs interface.

Trigger :

Flap of eth0 interface in OVS.

Flag enabled :

bundle-based-reconciliation-enabled=true.

Build:

ODL Controller - (Nitrogen) karaf-0.7.0-20170918.235023-1976
OVS Switch version - ovs 2.6.0

Procedure :

1)Bring up the OVS and Controller.
2)Pushed 5 flows via RestCall
3)Pushed statically a flow in OVS via "ovs-ofctl add-flow"
4)Flapped the eth0 interface of OVS.
5)After Flap openflow connection fails to get established.

root@mininet-vm4:~# sudo ovs-vsctl show

7e5d2616-8589-43bd-92ae-aebb2a0f475d
Manager "tcp:10.164.225.202:6640"
is_connected: true
Bridge br-int
Controller "tcp:10.164.225.202:6653"
Port br-int
Interface br-int
type: internal

root@mininet-vm4:~# sudo ovs-ofctl dump-flows br-int -OOpenflow13
OFPST_FLOW reply (OF1.3) (xid=0x2):

Attachments:

Inventory Config after Resync
Inventory Operational after Resync
vswitchd.log
karaf.log
Wireshark Capture in the Controller.



 Comments   
Comment by A Fathima Thasneem [ 22/Sep/17 ]

Attachment ovs-vswitchdlog.txt has been added with description: Logs after Resync

Comment by A Fathima Thasneem [ 22/Sep/17 ]

Attachment Capture_resync1.pcap has been added with description: WireShark Capture in Controller

Comment by A Fathima Thasneem [ 22/Sep/17 ]

Attachment Inventory Config after sync.txt has been added with description: Inventory Config

Comment by A Fathima Thasneem [ 22/Sep/17 ]

Attachment Inventory Operational after sync.txt has been added with description: Inventory Operational

Comment by A Fathima Thasneem [ 22/Sep/17 ]

Attachment karaf log.txt has been added with description: Karaf Log

Comment by Tomas Slusny [ 25/Sep/17 ]

Does it work with bundle-based-reconciliation flag set to false?

Comment by Sunil Kumar M S [ 25/Sep/17 ]

(In reply to Tomas Slusny from comment #5)
> Does it work with bundle-based-reconciliation flag set to false?

Yes Tomas, it works when bundle-based-reconciliation=false. We are currently debugging the issue.

Comment by Tomas Slusny [ 25/Sep/17 ]

Should this be blocker then? As bundle-based-reconciliation was never fully tested and by default it is disabled.

Comment by Sunil Kumar M S [ 25/Sep/17 ]

(In reply to Tomas Slusny from comment #7)
> Should this be blocker then? As bundle-based-reconciliation was never fully
> tested and by default it is disabled.

Yeah, this doesn't seem to be blocker. Only concern is controller disconnects after few attempts to resync in this case. Since submitter is testing bundle based resync, this will be blocker for their testing activity.

Comment by Tomas Slusny [ 26/Sep/17 ]

Okay then, as this scenario works with default configuration, lowering the priority to critical.

Comment by Sunil Kumar M S [ 13/Dec/17 ]

Issue is invalid as it is related to test environment and not to feature. Hence closing the bug

Generated at Wed Feb 07 20:33:48 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.