[NETVIRT-5] Instances in Compute node not able to reach dhcp Created: 17/Feb/16 Updated: 08/Apr/19 Resolved: 01/Sep/16 |
|
| Status: | Resolved |
| Project: | netvirt |
| Component/s: | None |
| Affects Version/s: | Beryllium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Venkatrangan Govindarajan | Assignee: | balakrishnan k |
| 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: | 5376 |
| Description |
|
Steps to recreate the problem: 1. Create Network 2. Create instances in such a way there are instances created in control node as well as compute node 3. ping the dhcp IP address from the instances local.conf :https://gist.github.com/gvranganvtn/ccbf76d20d18b6c670c7 ovs-vsctl show in both nodes: https://gist.github.com/gvranganvtn/f4cccecc76bb27195b06 dump-flows in both nodes: Test: 1.2.3.5 is the instacne created in compute node and 1.2.3.6 is the one on the control node. |
| Comments |
| Comment by Venkatrangan Govindarajan [ 17/Feb/16 ] |
|
Additional details of the scenario -> ODL in cluster mode -> Control Node up -> Created BNetwork in Openstack -> Bring up compute node -> create instances -> IP for instances got assigned, but the instacne in compute node not able to reach the dhcp IP |
| Comment by Sam Hague [ 17/May/16 ] |
|
Looking at flows, it seems the flow to get back from the compute node to the control node for the dhcp mac is not in table 110. Can we enable TRACE level on the netvirt code (at least for Of13Provider) and that might show us why that flow is not programmed.
ubuntu@odl-os-control-node:~/devstack$ sudo ovs-ofctl dump-flows br-int -OOpenFlow13
tun_id=0x426,dl_dst=fa:16:3e:9e:f6:70 actions=output:3
ubuntu@odl-os-compute-node:~/devstack$ sudo ovs-ofctl dump-flows br-int -OOpenFlow13
cookie=0x0, duration=1219.169s, table=110, n_packets=3, n_bytes=294, tun_id=0x426,dl_dst=fa:16:3e:de:47:a5 actions=output:1 |
| Comment by Venkatrangan Govindarajan [ 20/May/16 ] |
|
Disabled iptables in all compute nodes, all intances are reachable now when using ODL without clustering configutation. There seems to be problems exisitng when ODL is used as 3node, there are multiple exceptions observed while port event handling and other processing. Some important flows in pipeline is missed in all the openstack nodes. This needs to be investigated immediately to have a stable 3node job. |
| Comment by balakrishnan k [ 26/May/16 ] |
|
ODL1 log |
| Comment by balakrishnan k [ 26/May/16 ] |
|
Attachment ODL1.zip has been added with description: ODL1 log |
| Comment by balakrishnan k [ 26/May/16 ] |
|
Hi Sam, 1.Running 3 ODL controller as cluster with HA Proxy connected 1control and 2 compute nodes. first 2 VM(10.0.0.3, 10.0.0.4) instance getting IP and the flows are created properly in openstack nodes. enabled Debug log for southboudhandler and porthandler. OFPST_FLOW reply (OF1.3) (xid=0x2): |
| Comment by balakrishnan k [ 26/May/16 ] |
|
Attachment ODL2.zip has been added with description: ODL2 log |
| Comment by balakrishnan k [ 26/May/16 ] |
|
Attachment ODL3.zip has been added with description: ODL3 log |
| Comment by balakrishnan k [ 26/May/16 ] |
|
Attachment 26-5 FLows.txt has been added with description: dump flows for VM creation |
| Comment by Hideyuki Tai [ 27/Aug/16 ] |
|
I think one of reasons which caused this issue was a performance issue of the OVSDB Southbound plugin. The following patches have dramatically increased the performance of the OVSDB Southbound Plugin, so I think the rate of occurrence of this issue has been decreased now. |
| Comment by Prashanth Jakkam [ 01/Sep/16 ] |
|
We have tested with latest distribution after below patches were merged https://git.opendaylight.org/gerrit/#/c/43580/ Issue was not observed during multiple runs.We have observed, all created VM instances has acquired ip address. Following bugs has been raised for issues found in fail-over scenario testing. https://bugs.opendaylight.org/show_bug.cgi?id=6596 https://bugs.opendaylight.org/show_bug.cgi?id=6601 Hence,this bug can be closed. |