mpany this isn't a hwvtep test case is it? If not, could you push a standard upstream job netvirt-csit-1node- job that is not related to hwvtep and then post results? The hwvtep jobs are configured a little different so I want to rule out any issues there.

Hi Sam,

This suite is covers BGP establishment scenario using DCGW and in hwvtep job "tools_system_count" parameter is present which brings up DCGW VM.

But in netvirt-csit-1node- job, this parameter is not present.So, executing the suite using hwvtep job.

Please suggest me if i can use "netvirt-csit-1node- job" for DCGW related testcases.

Thanks,

Madhusmita

We can add the parameter if it makes sense. If these are not hwvtep specific tests, then we should add the parameter to the yaml and update the integration template. These would be dcgw deployments so also break them out in the project yaml so that the non-dcgw jobs don't spin up an unused tools vm. What you would do is add the param at the top under the openstack_system2_flavor, with value 0 as the default. Then add the same parameter under the functionality->gate-tdd-wip with the value set to how many tools vms you need. Update the integration template to use the vm_3_* stuff. That should work assuming the heat templates take the 0 count and don't do anything.

Are we sure this is a blocking bug (highest)?

If so what is it blocking? 

Hi Sam,

I followed the below steps to create dcgw job in non-hwvtep job :

-  In netvirt-csit-multi-openstack.yaml ,added the param at the top under the openstack_system2_flavor as :

openstack_system2_flavor: odl-standard-4
tools_system_count: 0
tools_system_image: ZZCI - Ubuntu 16.04 - mininet-ovs-26 - 20171208-1847

 Then added the same parameter under the functionality>gate-tdd-wip with the value set to 1 tools vms as 1 dcgw vm is needed as :

• anujgate-tdd-wip:
  testplan: '{project}-{topology}-tdd-wip-openstack.txt'
  schedule: ''
  tools_system_count: 1

-  Then, updated the integration template to use the vm_3_* stuff in integration-templates.yaml  :

Under job template : inttest-csit-openstack -> builder, added the below params :

vm_3_count: '{tools_system_count}'
vm_3_flavor: '{tools_system_flavor}'
vm_3_image: '{tools_system_image}'

Then created job : netvirt-csit-1node-openstack-pike-anujgate-tdd-wip-oxygen and started executing the job in sandbox.

But job is failing as it is not able to create tool system VM.

In environment variables 

Log : https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/netvirt-csit-1node-openstack-pike-anujgate-tdd-wip-oxygen/2/_build-enviroment-variables.log.gz

 https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/netvirt-csit-1node-openstack-pike-anujgate-tdd-wip-oxygen/5

Thanks,

Madhusmita

Hi,

VPN is not getting created after VPN deletion in fluorine build.

Thanks,

Madhusmita

Hi Madhu,
 
   I have analysed your attached logs (VPN_creation_fluorine_log) in the JIRA and observed JSON response[0] & [1] for L3VPN Creation and Deletion via ODL REST API after first time L3VPN was created and deleted successfully. Looks like you need to check your existing L3VPN instance having the RD 2200:2 as same as second time L3VPN creation request.
 
Please check whether if any existing L3VPN instance is having the RD as 2200:2 using ODL REST API get call [2]. Since i have validated the L3VPN creation and deletion of multiple times again and again with same ID in latest fluorine build (karaf-0.9.0-20180711.125024-1566) and i didn't observed any issues.
 
 
[0]: 
Creation of L3VPN log:
==================
{"errors":{"error":[

]}}
 
[1]:
Deletion of L3VPN log:
==================
{"errors":{"error":[

]}}
 
 
[2]:  
Get existing L3VPN:
==================
<POST> http://<ODL-IP>:8181/restconf/operations/neutronvpn:getL3VPN
 
 
Thanks and Regards,
Karthikeyan.

Hi Madhu, 
  I want to share one more point to check your setup before trying to create the same L3VPN instance again and again. Once you POST the JSON request for L3VPN instance delete, please check the L3VPN DS [0] to see the current VPN state. If it is marked as "pending_delete" then wait for few seconds to delete L3VPN instance completely. Hope this will solve your script issue.
 
 
[0]:
http://<ODL-IP>:8181/restconf/operational/odl-l3vpn:vpn-instance-op-data{ "vpn-instance-op-data": { "vpn-instance-op-data-entry": [ { "vrf-id": "2200:2", "vpnTargets": { "vpnTarget": [ { "vrfRTValue": "2200:2", "vrfRTType": "both" } ] }, "vpn-id": 100004, "vpn-instance-name": "4ae8cd92-48ca-49b5-94e1-b2921a261441", "bgpvpn-type": "BGPVPNExternal", "rd": [ "2200:2" ], "l3vni": 0, "ipv6-configured": false, "vpn-state": "pending_delete", "ipv4-configured": false } ] } }
Thanks & Regards,
Karthikeyan.

JayaPr : Could you please check if this is just a script issue as pointed out by Karthiikeyan above, and if so, close the Jira ?

Hi Faseela/Karthikeyan,

Script has been fixed some time back and is passing consistently.

Logs as below:

https://logs.opendaylight.org/sandbox/vex-yul-odl-jenkins-2/netvirt-csit-1node-0cmb-1ctl-2cmp-openstack-queens-gate-tdd-wip-sodium/7/robot-plugin/log_full.html

Not an issue in the code, CSIT script adjusted to fix the issue