HI Igor, That is strange. @Jose: Do you know what might be happening?
Could you check if you have the variable $creds? If you do "source $creds", what do you get? I will be busy this week in the OPNFV summit but could you try to execute the test directly without functest? To do so, inside the functest container, go to: /home/opnfv/repos/sfc/sfc/tests/functest And there, execute: source $cerds python run_tests.py That should execute the SFC tests Regards, Manuel On Fri, 2017-06-09 at 15:28 -0300, Igor Jochem Sanz wrote: > Hi Manuel. > > We ran everything as instructed, solved some issues but then we > stumbled > upon the messages below. It looks like we need a Jenkins build tag > to > proceed. Do you have any info on this? > > Thanks in advance. > Igor > > > root@c98fcb0eb6ae:~/repos/sfc/docs/release/scenarios# functest > testcase > run odl-sfc > 2017-06-09 18:17:27,034 - run_tests - INFO - > > 2017-06-09 18:17:27,034 - run_tests - INFO - > ============================================ > 2017-06-09 18:17:27,034 - run_tests - INFO - Running test case > 'odl-sfc'... > 2017-06-09 18:17:27,034 - run_tests - INFO - > ============================================ > 2017-06-09 18:17:27,035 - openstack_snapshot - INFO - Generating > OpenStack snapshot... > 2017-06-09 18:17:27,642 - openstack_utils - INFO - > OS_IDENTITY_API_VERSION is set in env as '3' > 2017-06-09 18:18:30,183 - functest_utils - ERROR - The command 'cd > /home/opnfv/repos/sfc/sfc/tests/functest && python ./run_tests.py' > failed. > 2017-06-09 18:18:30,184 - sfc - INFO - sfc FAILED > 2017-06-09 18:18:30,184 - functest_utils - INFO - Impossible to > retrieve > the build tag > 2017-06-09 18:18:30,184 - functest_utils - INFO - Impossible to > retrieve > the build tag > 2017-06-09 18:18:30,220 - functest_utils - INFO - > **************************************** > sfc/functest-odl-sfc results > > **************************************** > DB: http://testresults.opnfv.org/test/api/v1 > pod: localhost > version: unknown > scenario: os-odl_l2-sfc-noha > status: FAIL > build tag: none > details: {} > > 2017-06-09 18:18:30,220 - sfc - INFO - Test result is stored in > '/home/opnfv/functest/results/sfc.log' > 2017-06-09 18:18:30,220 - openstack_clean - INFO - Cleaning > OpenStack > resources... > 2017-06-09 18:18:30,223 - openstack_utils - INFO - > OS_IDENTITY_API_VERSION is set in env as '3' > 2017-06-09 18:18:36,956 - run_tests - INFO - Test execution time: > 01:09 > 2017-06-09 18:18:36,957 - run_tests - ERROR - The test case 'odl- > sfc' > failed. > 2017-06-09 18:18:36,957 - run_tests - INFO - Execution exit value: > Result.EX_ERROR > 2017-06-09 18:18:37,010 - functest_utils - ERROR - The command > 'python > /home/opnfv/repos/functest/functest/ci/run_tests.py -t odl-sfc' > failed. > > > > Em 2017-06-05 04:35, Manuel Buil escreveu: > > > > HI Igor, > > > > Interesting... it seems the guys from functest are changing stuff. > > While I investigate this, can you try with the Danube1.0 image > > please? > > > > That means executing this as the first step: > > > > docker pull opnfv/functest:danube.1.0 > > > > Instead of "docker pull opnfv/functest" which points to the master > > branch. > > > > And then when creating the container with "docker run..." point to > > the > > danube.1.0 image. > > > > Regards, > > Manuel > > > > On Sat, 2017-06-03 at 13:39 -0300, Igor Jochem Sanz wrote: > > > > > > Hi Manuel, > > > > > > At the moment I'm trying to understand how things work and > > > checking > > > its > > > stability in a baremetal deployment. I have plans for testing > > > some > > > VNFs > > > chains in different scenarios later for academic purposes. > > > > > > I've tried the functest you suggested. I've got an error when > > > running > > > the testcase on step 6. > > > > > > functest.ci.run_tests - ERROR - Unknown test case or tier 'odl- > > > sfc', > > > or > > > not supported by the given scenario 'os-odl_l2-sfc-ha'. > > > functest.utils.functest_utils - ERROR - The command 'python > > > /home/opnfv/repos/functest/functest/ci/run_tests.py -t odl-sfc' > > > failed. > > > > > > I checked for the tier list and there is no testcase 'odl-sfc' in > > > the > > > given docker image. > > > > > > functest tier list > > > - 0. healthcheck: > > > ['connection_check', 'api_check', 'snaps_health_check'] > > > - 1. smoke: > > > ['vping_ssh', 'vping_userdata', 'tempest_smoke_serial', > > > 'rally_sanity', 'refstack_defcore', 'odl', 'snaps_smoke'] > > > - 2. features: > > > ['promise'] > > > - 3. components: > > > ['tempest_full_parallel', 'rally_full'] > > > - 4. vnf: > > > ['cloudify_ims'] > > > > > > Do you know how can I get the testcases that are missing? > > > > > > I also noted credendials should be pointed in the env variable > > > $openstack_creds and not $creds as asked by the script. > > > > > > Thanks for your support, > > > > > > Sanz > > > > > > > > > > > > Em 2017-06-01 12:32, Manuel Buil escreveu: > > > > > > > > > > > > Hi Sanz, > > > > > > > > I am not sure if those instructions will work :(. > > > > > > > > These ones should work because we tested them two months ago > > > > and if > > > > they don't work we can help you: > > > > > > > > https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+case > > > > s > > > > > > > > However, note that those instructions will automatically deploy > > > > SFs > > > > and > > > > chains, run several tests, check if things work and clean up. > > > > So > > > > depending on what you want to do, you should change a bit the > > > > code > > > > (we > > > > can help you). Let us understand your ambitions: would you like > > > > to > > > > run > > > > something specific or are you currently trying to understand > > > > how > > > > things > > > > work? > > > > > > > > Regards, > > > > Manuel > > > > > > > > > > > > > > > > On Thu, 2017-06-01 at 12:06 -0300, Igor Jochem Sanz wrote: > > > > > > > > > > > > > > > Hello guys, I'm new here. > > > > > > > > > > Does anyone can confirm if the following functionality test > > > > > for > > > > > SFC > > > > > on > > > > > opnfv it is working on Danube 2.0? > > > > > > > > > > https://github.com/trozet/sfc-random/blob/master/tacker_sfc_a > > > > > pex_ > > > > > walk > > > > > through.txt > > > > > > > > > > I've tested it over an opnfv danube 2.0 install through fuel > > > > > deployment > > > > > and it didn't work. > > > > > > > > > > On the last step NSH tagged packets are not matching with the > > > > > created > > > > > rules, although they are reaching the virtual switch. > > > > > > > > > > Thanks in advance, > > > > > > > > > > Sanz > > > > > _______________________________________________ > > > > > opnfv-tech-discuss mailing list > > > > > [email protected] > > > > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > > > _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
