[OPNFLWPLUG-835] Bridge br-int added but flows not created after OVS stop and start in control node and compute nodes Created: 30/Dec/16 Updated: 27/Sep/21 Resolved: 06/Mar/17 |
|
| Status: | Resolved |
| Project: | OpenFlowPlugin |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | ranjithkumar_t | Assignee: | Bertrand Low |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 7462 |
| Description |
|
ODL Version : distribution-karaf-0.5.2-Boron-SR2 Openstack Version : mitaka Setup Details : 3 ODL Nodes + 1 Control Node + 2 Compute Nodes Steps to Reproduce: 2. Stop All 3 ODLs 3. Clean data, journal and snapshot for all 3 ODL nodes and start ODL 4. Wait for a while ODL starting log back to normal 5. OVS setting 6. OVS stop and start Observation: Please find the attached files for karaf logs and OVS details. |
| Comments |
| Comment by ranjithkumar_t [ 30/Dec/16 ] |
|
Attachment karaf logs.zip has been added with description: Karaf logs for your reference |
| Comment by ranjithkumar_t [ 30/Dec/16 ] |
|
Attachment OVS details.zip has been added with description: OVS details for your reference |
| Comment by Bertrand Low [ 13/Jan/17 ] |
|
The problem is the immediate succession of starting the ovs-vswitchd process after stopping it when the device is connected to an ODL cluster; using “systemctl restart openvswitch” has the same effect. This issue is not observed in a non-clustered setup, single ODL setup. If there is even a 2s (two second) delay between stopping and starting, installation of br-int and flows is successful. Resetting the ovs-manager appears to successfully install br-int and the flows. |
| Comment by Bertrand Low [ 19/Jan/17 ] |
|
Please see related The difference compared to I've attached a couple of logs: one which shows what happens when the openvswitch process is restarted on the device and br-int gets successfully installed but not the flows, and also a successful case where the flows get installed as well (FRM sees the node as added due to the timing order of the events). In both of these log captures, the controller has issues connecting to odl35, but this may prove not to be meaningful. |
| Comment by Bertrand Low [ 19/Jan/17 ] |
|
Attachment NoFlows.tar.gz has been added with description: no flows installed |
| Comment by Bertrand Low [ 19/Jan/17 ] |
|
Attachment Success.tar.gz has been added with description: successful flow installation after restarting openvswitch |
| Comment by Ananthi Palaniswamy [ 30/Jan/17 ] |
|
Tested the patch https://git.opendaylight.org/gerrit/#/c/51058/ Attached karaf logs. |
| Comment by Ananthi Palaniswamy [ 30/Jan/17 ] |
|
Attachment ODL1karaf log -10.106.138.68.zip has been added with description: ODL1 karaf log |
| Comment by Ananthi Palaniswamy [ 30/Jan/17 ] |
|
Attachment ODL2 karaf log-10.106.138.110.zip has been added with description: ODL2 karaf log |
| Comment by Ananthi Palaniswamy [ 30/Jan/17 ] |
|
Attachment ODL3 karaf log-10.106.138.154.zip has been added with description: ODL3 karaf log |
| Comment by Ananthi Palaniswamy [ 30/Jan/17 ] |
|
Attachment OVS Control node details.jpg has been added with description: OVS details Control node |
| Comment by Ananthi Palaniswamy [ 31/Jan/17 ] |
|
Please ignore logs added on 30.0.2017, |
| Comment by Bertrand Low [ 03/Feb/17 ] |
|
Jozef's following patches:
appear to resolve this bug. The above patches can be ported over to stable/boron when they are ready. |
| Comment by Bertrand Low [ 01/Mar/17 ] |
|
Anil's fix for 7736 also appears to address this issue: https://git.opendaylight.org/gerrit/#/c/51489/ Will confirm the findings before closing the bugs |
| Comment by Bertrand Low [ 06/Mar/17 ] |
|
Fixed with Anil's patch for |