HI Jose, The error message "Exception: Cannot establish connection to the installer node!" remains.
I edited the fuel and jumphost iptables to release all tcp and up traffic (INPUT, FORWARD and OUTPUP). -A INPUT -p tcp -j ACCEPT -A INPUT -p udp -j ACCEPT -A FORWARD -p tcp -j ACCEPT -A FORWARD -p udp -j ACCEPT -A OUTPUT -p tcp -j ACCEPT -A OUTPUT -p udp -j ACCEPT *I am able to establish ssh connections from my docker image to the fuel server* root@node-8:~# docker run --privileged=true -id -e INSTALLER_TYPE=fuel -e INSTALLER_IP=10.20.0.2 -e DEPLOY_SCENARIO=os-odl_l2-sfc-ha -e CI_DEBUG=false --name sfc100 opnfv/functest:danube.1.0 ... root@node-8:~# sudo docker exec -ti sfc100 bash root@a3a442f842ff:~# ssh -l root 10.20.0.2 [email protected]'s password: Last login: Fri Jun 16 04:47:19 2017 from 10.20.0.8 [root@fuel-danube ~]# #root@a3a442f842ff:~# functest env prepare It seems that the environment has been already prepared. Do you want to do it again? [y|n] n *I also have the openstack credentials exported correctly* root@a3a442f842ff:~# openstack network list +--------------------------------------+--------------------+--------------------------------------+ | ID | Name | Subnets | +--------------------------------------+--------------------+--------------------------------------+ | 442f9ae4-d10e-453a-8686-0990ffafb82c | admin_floating_net | d46017b0-1b7c-4591-8b73-f4cee13fb590 | | e6b41188-f1c1-4d23-ba36-41b5c10db622 | admin_internal_net | d9ec4c77-01fb-4184-9cc3-d573f3f90104 | +--------------------------------------+--------------------+--------------------------------------+ However, we still have the same problem. I'm working with Sanz, following all the steps recommended in the Functest documentation, but so far we do not know if the SFC is working because we always have the same error We have one controller (roles: Controller, Telemetry - MongoDB, Tacker VNF manager, OpenDaylight) and three compute nodes (roles: Compute, Ceph OSD) in our OPNFV setup. root@a3a442f842ff:~# functest testcase list |grep odl odl odl-sfc root@a3a442f842ff:~# functest testcase run odl-sfc 2017-06-16 05:08:24,782 - run_tests - INFO - 2017-06-16 05:08:24,782 - run_tests - INFO - ============================================ 2017-06-16 05:08:24,782 - run_tests - INFO - Running test case 'odl-sfc'... 2017-06-16 05:08:24,782 - run_tests - INFO - ============================================ 2017-06-16 05:08:24,783 - openstack_snapshot - INFO - Generating OpenStack snapshot... 2017-06-16 05:08:25,385 - openstack_utils - INFO - OS_IDENTITY_API_VERSION is set in env as '3' 2017-06-16 05:08:30,994 - functest_utils - ERROR - The command 'cd /home/opnfv/repos/sfc/sfc/tests/functest && python ./run_tests.py' failed. 2017-06-16 05:08:30,994 - sfc - INFO - sfc FAILED 2017-06-16 05:08:30,995 - functest_utils - INFO - Unable to retrieve the POD name from environment. Using pod name 'unknown-pod' 2017-06-16 05:08:30,995 - functest_utils - INFO - Impossible to retrieve the build tag 2017-06-16 05:08:30,995 - functest_utils - INFO - Impossible to retrieve the build tag 2017-06-16 05:08:31,029 - functest_utils - INFO - **************************************** sfc/functest-odl-sfc results **************************************** DB: http://testresults.opnfv.org/test/api/v1 pod: unknown-pod version: unknown scenario: os-odl_l2-sfc-ha status: FAIL build tag: none details: {} 2017-06-16 05:08:31,029 - sfc - INFO - Test result is stored in '/home/opnfv/functest/results/sfc.log' 2017-06-16 05:08:31,029 - openstack_clean - INFO - Cleaning OpenStack resources... 2017-06-16 05:08:31,032 - openstack_utils - INFO - OS_IDENTITY_API_VERSION is set in env as '3' 2017-06-16 05:08:37,685 - run_tests - INFO - Test execution time: 00:12 2017-06-16 05:08:37,685 - run_tests - ERROR - The test case 'odl-sfc' failed. 2017-06-16 05:08:37,686 - run_tests - INFO - Execution exit value: Result.EX_ERROR 2017-06-16 05:08:37,729 - functest_utils - ERROR - The command 'python /home/opnfv/repos/functest/functest/ci/run_tests.py -t odl-sfc' failed. root@a3a442f842ff:~# cat /home/opnfv/functest/results/sfc.log 2017-06-16 05:08:30,847 - SSH utils - ERROR - Authentication failed. Traceback (most recent call last): File "./run_tests.py", line 189, in <module> main(report=args.report) File "./run_tests.py", line 81, in main installer_pwd=COMMON_CONFIG.installer_password) File "/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py", line 42, in get_handler installer_pwd=installer_pwd) File "/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py", line 26, in __init__ pkey_file=None) File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 325, in __init__ 'Cannot establish connection to the installer node!') Exception: Cannot establish connection to the installer node! root@a3a442f842ff:~# exit Thanks for your support, Leopoldo Mauricio On Wed, Jun 14, 2017 at 9:00 AM, <[email protected] > wrote: > Send opnfv-tech-discuss mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of opnfv-tech-discuss digest..." > > > Today's Topics: > > 1. Re: opnfv-tech-discuss Digest, Vol 34, Issue 11 (Jose Lausuch) > 2. [APEX] Apex virtual deployment install fails with error > (Srikanth Vavilapalli) > 3. Re: [APEX] Apex virtual deployment install fails with error > (Feng Pan) > 4. Canceled: opnfvdocs project meeting (updated GoToMeeting > link) (Sofia Wallin) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 14 Jun 2017 01:30:40 +0000 > From: Jose Lausuch <[email protected]> > To: Leopoldo Mauricio <[email protected]> > Cc: "[email protected]" > <[email protected]> > Subject: Re: [opnfv-tech-discuss] opnfv-tech-discuss Digest, Vol 34, > Issue 11 > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > If you can access from your jumphost and not from the container as such, > you might have some iptables configured preventing that. > Please make sure and remove any ip table rejecting traffic to the fuelX > bridges, specially the bridge used for pxe network (10.20.0.x). > > Regards, > Jose > > > > On 14 Jun 2017, at 02:23, Leopoldo Mauricio <[email protected]<mailto: > [email protected]>> wrote: > > Hi Jose, > > Really thanks for your attention. Talking about my environment: > > My fuel (that is a baremetal host) is using the ip 10.20.0.2 and I have > access to its from my jumphost (also a baremetal host with ip address > 10.20.0.8) > > root@476c23c24e90:~# ssh 10.20.0.2 > The authenticity of host '10.20.0.2 (10.20.0.2)' can't be established. > ECDSA key fingerprint is fe:25:c3:e2:64:76:c8:a1:42:e5:cc:a1:23:21:35:de. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known hosts. > [email protected]<mailto:[email protected]>'s password: > Last login: Tue Jun 13 14:29:50 2017 from ... > [root@fuel-danube ~]# exit > > > When I look at the results of tcpdump (while "python run_tests.py" is > running) It seems that jumphost is able to establish ssh connections with > fuel host. > > Despite this, the python paramiko is warning of the error: AttributeError: > 'NoneType' object has no attribute 'open_session' > > > Do you believe the test code may be terminating the ssh connection ahead > of time? > Is there any chance that this is the source of the problem? > > > > > TCPDUMP result: > > [root@fuel-danube ~]# tcpdump -i any host 10.20.0.8 and port 22 -nn |grep > "10.20.0.2.22" > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > listening on any, link-type LINUX_SLL (Linux cooked), capture size 65535 > bytes > 17:27:42.919129 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [S], seq > 895652737, win 29200, options [mss 1460,sackOK,TS val 37906111 ecr > 0,nop,wscale 7], length 0 > 17:27:42.919170 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [S.], seq > 2875078289, ack 895652738, win 28960, options [mss 1460,sackOK,TS val > 952280858 ecr 37906111,nop,wscale 7], length 0 > 17:27:42.919403 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [.], ack 1, win > 229, options [nop,nop,TS val 37906111 ecr 952280858], length 0 > 17:27:42.920774 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [P.], seq 1:25, > ack 1, win 229, options [nop,nop,TS val 37906111 ecr 952280858], length 24 > 17:27:42.920809 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [.], ack 25, win > 227, options [nop,nop,TS val 952280860 ecr 37906111], length 0 > 17:27:42.935195 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [P.], seq 1:24, > ack 25, win 227, options [nop,nop,TS val 952280874 ecr 37906111], length 23 > 17:27:42.935405 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [.], ack 24, win > 229, options [nop,nop,TS val 37906115 ecr 952280874], length 0 > 17:27:42.936268 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [P.], seq 25:665, > ack 24, win 229, options [nop,nop,TS val 37906115 ecr 952280874], length 640 > 17:27:42.938730 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [P.], seq 24:600, > ack 665, win 237, options [nop,nop,TS val 952280878 ecr 37906115], length > 576 > 17:27:42.947660 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [P.], seq > 665:809, ack 600, win 238, options [nop,nop,TS val 37906118 ecr 952280878], > length 144 > 17:27:42.951277 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [P.], seq > 600:1320, ack 809, win 247, options [nop,nop,TS val 952280890 ecr > 37906118], length 720 > 17:27:42.989845 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [.], ack 1320, > win 249, options [nop,nop,TS val 37906129 ecr 952280890], length 0 > 17:27:43.700018 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [P.], seq > 809:825, ack 1320, win 249, options [nop,nop,TS val 37906306 ecr > 952280890], length 16 > 17:27:43.739603 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [.], ack 825, win > 247, options [nop,nop,TS val 952281679 ecr 37906306], length 0 > 17:27:43.739865 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [P.], seq > 825:889, ack 1320, win 249, options [nop,nop,TS val 37906316 ecr > 952281679], length 64 > 17:27:43.739904 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [.], ack 889, win > 247, options [nop,nop,TS val 952281679 ecr 37906316], length 0 > 17:27:43.739979 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [P.], seq > 1320:1384, ack 889, win 247, options [nop,nop,TS val 952281679 ecr > 37906316], length 64 > 17:27:43.740138 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [.], ack 1384, > win 249, options [nop,nop,TS val 37906316 ecr 952281679], length 0 > 17:27:43.740822 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [P.], seq > 889:985, ack 1384, win 249, options [nop,nop,TS val 37906316 ecr > 952281679], length 96 > ... > ... > 17:27:48.395015 IP 10.20.0.2.22 > 10.20.0.8.34998: Flags [F.], seq 4504, > ack 1242, win 247, options [nop,nop,TS val 952286334 ecr 37907478], length 0 > 17:27:48.395201 IP 10.20.0.8.34998 > 10.20.0.2.22: Flags [.], ack 4505, > win 317, options [nop,nop,TS val 37907480 ecr 952286334], length 0 > 17:27:48.454912 IP 10.20.0.8.35022 > 10.20.0.2.22: Flags [F.], seq 1817, > ack 4088, win 305, options [nop,nop,TS val 37907495 ecr 952286293], length 0 > 17:27:48.458424 IP 10.20.0.2.22 > 10.20.0.8.35022: Flags [F.], seq 4088, > ack 1818, win 247, options [nop,nop,TS val 952286397 ecr 37907495], length 0 > 17:27:48.458654 IP 10.20.0.8.35022 > 10.20.0.2.22: Flags [.], ack 4089, > win 305, options [nop,nop,TS val 37907496 ecr 952286397], length 0 > > > > Thanks for your support, > > Leopoldo Mauricio > > > On Tue, Jun 13, 2017 at 12:42 PM, Jose Lausuch <[email protected]< > mailto:[email protected]>> wrote: > Hi Leopoldo, > > The SFC test case needs to access the deployment to perform some actions. > Do you have access to Fuel VM from your container? We use 10.20.0.2 by > default. If you use a different IP you will need to specify it along with > the password in the configuration. > > Regards, > Jose > > > > On 13 Jun 2017, at 23:15, Leopoldo Mauricio <[email protected]<mailto: > [email protected]>> wrote: > > Hi Morgan and Manuel, > > I've got the same error that Sanz has informed using both danube.1.0 and > stable docker images. > > > > When I do "python run_tests.py" > > root@476c23c24e90:~# cd /home/opnfv/repos/sfc/sfc/tests/functest/ > root@476c23c24e90:~/repos/sfc/sfc/tests/functest# python run_tests.py > > I have the following error, which can also be found inside the logs > > root@476c23c24e90:~# cat /home/opnfv/functest/results/sfc.log > > 2017-06-13 14:56:34,607 - paramiko.transport - ERROR - Secsh channel 1 > open FAILED: No route to host: Connect failed > 2017-06-13 14:56:34,610 - SSH utils - ERROR - (2, 'Connect failed') > Traceback (most recent call last): > File "./run_tests.py", line 189, in <module> > main(report=args.report) > File "./run_tests.py", line 81, in main > installer_pwd=COMMON_CONFIG.installer_password) > File "/home/opnfv/repos/releng/modules/opnfv/deployment/factory.py", > line 42, in get_handler > installer_pwd=installer_pwd) > File "/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py", > line 26, in __init__ > pkey_file=None) > File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", > line 327, in __init__ > self.nodes = self.get_nodes() > File "/home/opnfv/repos/releng/modules/opnfv/deployment/fuel/adapter.py", > line 159, in get_nodes > id, ip, name, status, roles, ssh_client, dict) > File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", > line 136, in __init__ > sys_info = self.get_system_info() > File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", > line 246, in get_system_info > memory = self.run_cmd(cmd).partition('MemTotal:')[-1].strip().encode() > File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", > line 182, in run_cmd > _, stdout, stderr = (self.ssh_client.exec_command(cmd)) > File "/usr/local/lib/python2.7/dist-packages/paramiko/client.py", line > 435, in exec_command > chan = self._transport.open_session(timeout=timeout) > AttributeError: 'NoneType' object has no attribute 'open_session' > > > Thanks for your support, > > Leopoldo Mauricio > > > On Sun, Jun 11, 2017 at 9:00 AM, <opnfv-tech-discuss-request@ > lists.opnfv.org<mailto:[email protected]>> wrote: > Send opnfv-tech-discuss mailing list submissions to > [email protected]<mailto:opnfv-tech- > [email protected]> > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > or, via email, send a message with subject or body 'help' to > [email protected]<mailto:opnfv- > [email protected]> > > You can reach the person managing the list at > [email protected]<mailto:opnfv- > [email protected]> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of opnfv-tech-discuss digest..." > > > Today's Topics: > > 1. Re: SFC functionality test (Manuel Buil) > 2. RE : SFC functionality test ([email protected]<mailto: > [email protected]>) > 3. Details for Summit registration etc (SULLIVAN, BRYAN L) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sat, 10 Jun 2017 17:41:10 +0200 > From: Manuel Buil <[email protected]<mailto:[email protected]>> > To: Igor Jochem Sanz <[email protected]<mailto:[email protected]>>, Jose > Lausuch > <[email protected]<mailto:[email protected]>> > Cc: [email protected]<mailto:opnfv-tech- > [email protected]> > Subject: Re: [opnfv-tech-discuss] SFC functionality test > Message-ID: <[email protected]<mailto:1497109270.2763.4. > [email protected]>> > Content-Type: text/plain; charset="UTF-8" > > 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]<mailto:opnfv-tech- > [email protected]> > > > > > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > > > > > > > > ------------------------------ > > Message: 2 > Date: Sun, 11 Jun 2017 00:14:20 +0000 > From: <[email protected]<mailto:[email protected]>> > To: Manuel Buil <[email protected]<mailto:[email protected]>>, Igor Jochem Sanz > <[email protected]<mailto:[email protected]>>, > "Jose Lausuch" <[email protected]<mailto: > [email protected]>> > Cc: "[email protected]<mailto:opnfv-tech- > [email protected]>" > <[email protected]<mailto:opnfv-tech- > [email protected]>> > Subject: [opnfv-tech-discuss] RE : SFC functionality test > Message-ID: > <457_1497140060_593C8B5C_457_14199_1_vfqv84dnt2so0opfnah1p1fo. > [email protected]<mailto:457_1497140060_ > 593C8B5C_457_14199_1_vfqv84dnt2so0opfnah1p1fo.1497140055697@email.android. > com>> > > Content-Type: text/plain; charset="iso-8859-1" > > Hi > > BuildTag is used to push the result in the test DB in CI mode. > The info that it is missing is printed as INFO so there is no problem on > this side > > Regarding the logs I would suggest to have a look at the logs in > /home/opnfv/functest/results/sfc.log > > Morgan > > > > > Envoy? de mon Galaxy Note 4 d'Orange > > > -------- Message d'origine -------- > De : Manuel Buil <[email protected]<mailto:[email protected]>> > Date : 10/06/2017 23:40 (GMT+08:00) > ? : Igor Jochem Sanz <[email protected]<mailto:[email protected]>>, Jose > Lausuch <[email protected]<mailto:[email protected]>> > Cc : [email protected]<mailto:opnfv-tech- > [email protected]> > Objet : Re: [opnfv-tech-discuss] SFC functionality test > > 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]<mailto:opnfv-tech- > [email protected]> > > > > > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > > > > > > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected]<mailto:opnfv-tech- > [email protected]> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > ____________________________________________________________ > _____________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez > recu ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and > delete this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170611/0befaf47/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Sun, 11 Jun 2017 03:06:31 +0000 > From: "SULLIVAN, BRYAN L" <[email protected]<mailto:[email protected]>> > To: "[email protected]<mailto:opnfv-tech- > [email protected]>" > <[email protected]<mailto:opnfv-tech- > [email protected]>>, Brandon Wick > <[email protected]<mailto:[email protected]>> > Subject: [opnfv-tech-discuss] Details for Summit registration etc > Message-ID: > <59A39E87EA9F964A836299497B686C355E207A7F@CAFRFD1MSGUSRJD. > ITServices.sbc.com<mailto:59A39E87EA9F964A836299497B686C355E > [email protected]>> > > Content-Type: text/plain; charset="us-ascii" > > Hi Brandon, > > I may have missed an email, but has there been a logistics email sent for > the summit yet, e.g. when/where to pick up badges, wifi info, etc ? > > Thanks, > Bryan Sullivan | AT&T > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170611/a0de6c77/attachment-0001.html> > > ------------------------------ > > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected]<mailto:opnfv-tech- > [email protected]> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > End of opnfv-tech-discuss Digest, Vol 34, Issue 11 > ************************************************** > > > > -- > Leopoldo Mauricio > Tel: +5521 9 7959-5050 > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected]<mailto:opnfv-tech- > [email protected]> > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > > -- > Leopoldo Mauricio > Tel: +5521 9 7959-5050 > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170614/ebcea707/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Tue, 13 Jun 2017 21:50:41 +0000 > From: Srikanth Vavilapalli <[email protected]> > To: "[email protected]" > <[email protected]> > Subject: [opnfv-tech-discuss] [APEX] Apex virtual deployment install > fails with error > Message-ID: > <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > Hi > > I am trying to setup APEX virtual deployment on a centos7 VM by following > the instructions from http://docs.opnfv.org/en/ > stable-danube/submodules/apex/docs/release/installation/ > virtualinstall.html. > > At a high level: > > 1. Created a VM with Centos 7 on an ubuntu server > 2. Installed RDO RPM: https://www.rdoproject.org/repos/rdo-release.rpm > 3. Installed APEX RPMs (version 5.0-20170608) from opnfv artifacts > 4. sudo opnfv-deploy -v --virtual-computes 1 -n > /etc/opnfv-apex/network_settings.yaml > -d /etc/opnfv-apex/os-odl-bgpvpn-noha.yaml > > The opnfv-deploy script ran for nearly 90mins or so after which it > returned the following error log (attached full log): > > Configuring undercloud and discovering nodes > Waiting for messages on queue '18d292d8-e4c2-4bde-a6b0-88557f636f4e' with > no timeout. > Waiting for messages on queue '18d292d8-e4c2-4bde-a6b0-88557f636f4e' with > no timeout. > Started Mistral Workflow tripleo.baremetal.v1.register_or_update. > Execution ID: 2f658b2a-29ea-4eb8-a877-86f19bebffa8 > Successfully registered node UUID 121aaeca-ab9a-47cb-856b-d38521758e85 > Successfully registered node UUID 0023532c-1548-44a9-9bc1-fcbf8be18513 > Started Mistral Workflow tripleo.baremetal.v1.provide. Execution ID: > 12606ed5-5320-4571-890d-89570c7512d0 > Successfully set all nodes to available. > Configuring nameserver on ctlplane network > Executing overcloud deployment, this could run for an extended period > without output. > Error: The following files were not found: /usr/share/openstack-tripleo- > heat-templates/environments/neutron-opendaylight-bgpvpn.yaml > ERROR: The Stack (overcloud) could not be found. > [vagrant@jumphost ~]$ > > Can anyone plz help me with this and point me if I am missing any step in > the process? > > Thanks > Srikanth > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170613/c6b6b4fc/attachment-0001.html> > -------------- next part -------------- > An embedded and charset-unspecified text was scrubbed... > Name: opnfv_apex_install_log.txt > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170613/c6b6b4fc/attachment-0001.txt> > > ------------------------------ > > Message: 3 > Date: Tue, 13 Jun 2017 21:40:57 -0400 > From: Feng Pan <[email protected]> > To: Srikanth Vavilapalli <[email protected]> > Cc: "[email protected]" > <[email protected]> > Subject: Re: [opnfv-tech-discuss] [APEX] Apex virtual deployment > install fails with error > Message-ID: > <CALfdj+4mWf+a5k31QfUutJrq0irzE8mRDXqZEMaAh > [email protected]> > Content-Type: text/plain; charset="utf-8" > > Hi Srikanth, > > Please use rpms from Danube branch and not master branch, most scenarios > are not yet enabled on master, since we moved from Newton to Ocata release > of Openstack. > > Thanks > Feng > > On Tue, Jun 13, 2017 at 5:50 PM, Srikanth Vavilapalli < > [email protected]> wrote: > > > Hi > > > > > > > > I am trying to setup APEX virtual deployment on a centos7 VM by following > > the instructions from http://docs.opnfv.org/en/ > > stable-danube/submodules/apex/docs/release/installation/ > > virtualinstall.html. > > > > > > > > At a high level: > > > > 1. Created a VM with Centos 7 on an ubuntu server > > 2. Installed RDO RPM: https://www.rdoproject.org/ > repos/rdo-release.rpm > > 3. Installed APEX RPMs (version 5.0-20170608) from opnfv artifacts > > 4. sudo opnfv-deploy -v --virtual-computes 1 -n > > /etc/opnfv-apex/network_settings.yaml -d > /etc/opnfv-apex/os-odl-bgpvpn- > > noha.yaml > > > > > > > > The opnfv-deploy script ran for nearly 90mins or so after which it > > returned the following error log (attached full log): > > > > > > > > Configuring undercloud and discovering nodes > > > > Waiting for messages on queue '18d292d8-e4c2-4bde-a6b0-88557f636f4e' > with > > no timeout. > > > > Waiting for messages on queue '18d292d8-e4c2-4bde-a6b0-88557f636f4e' > with > > no timeout. > > > > Started Mistral Workflow tripleo.baremetal.v1.register_or_update. > > Execution ID: 2f658b2a-29ea-4eb8-a877-86f19bebffa8 > > > > Successfully registered node UUID 121aaeca-ab9a-47cb-856b-d38521758e85 > > > > Successfully registered node UUID 0023532c-1548-44a9-9bc1-fcbf8be18513 > > > > Started Mistral Workflow tripleo.baremetal.v1.provide. Execution ID: > > 12606ed5-5320-4571-890d-89570c7512d0 > > > > Successfully set all nodes to available. > > > > Configuring nameserver on ctlplane network > > > > Executing overcloud deployment, this could run for an extended period > > without output. > > > > Error: The following files were not found: /usr/share/openstack-tripleo- > > heat-templates/environments/neutron-opendaylight-bgpvpn.yaml > > > > ERROR: The Stack (overcloud) could not be found. > > > > [vagrant@jumphost ~]$ > > > > > > > > Can anyone plz help me with this and point me if I am missing any step in > > the process? > > > > > > > > Thanks > > > > Srikanth > > > > _______________________________________________ > > opnfv-tech-discuss mailing list > > [email protected] > > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170613/c3b4ede2/attachment-0001.html> > > ------------------------------ > > Message: 4 > Date: Wed, 14 Jun 2017 04:35:36 +0000 > From: Sofia Wallin <[email protected]> > To: TECH-DISCUSS OPNFV <[email protected]> > Cc: Scott Mansfield <[email protected]>, "Reid Cheng > \(xincheng\)" <[email protected]>, Charles Hale > <[email protected]>, Mario Torrecillas Rodriguez > <[email protected]> > Subject: [opnfv-tech-discuss] Canceled: opnfvdocs project meeting > (updated GoToMeeting link) > Message-ID: > <AM5PR0701MB288462671CCEDF01EDE4FB0FE4C30@AM5PR0701MB2884. > eurprd07.prod.outlook.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > Cancelled due to the summit. > > *************************************** > > Updated with new GoToMeeting link > > > > *************************************** > Welcome to join the opnfvdocs meeting. > > > > > Intention is to cover: > Project backlog and progress > Questions and issues > > > > > Please join my meeting from your computer, tablet or smartphone. > https://global.gotomeeting.com/join/819733085 > > You can also dial in using your phone. > United States +1 (312) 757-3126 > > Access Code: 819-733-085 > > More phone numbers > Australia +61 2 8355 1040 > Austria +43 7 2088 0034 > Belgium +32 (0) 28 93 7018 > Canada +1 (647) 497-9350 > Denmark +45 69 91 88 64 > Finland +358 (0) 923 17 0568 > France +33 (0) 170 950 592 > Germany +49 (0) 692 5736 7211 > Ireland +353 (0) 15 360 728 > Italy +39 0 247 92 13 01 > Netherlands +31 (0) 208 080 219 > New Zealand +64 9 280 6302 > Norway +47 75 80 32 07 > Spain +34 911 82 9906 > Sweden +46 (0) 853 527 836 > Switzerland +41 (0) 435 0167 13 > United Kingdom +44 (0) 330 221 0086 > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170614/ee9e9b7c/attachment-0001.html> > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: text/calendar > Size: 6178 bytes > Desc: not available > URL: <http://lists.opnfv.org/pipermail/opnfv-tech-discuss/ > attachments/20170614/ee9e9b7c/attachment-0001.ics> > > ------------------------------ > > _______________________________________________ > opnfv-tech-discuss mailing list > [email protected] > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > > > End of opnfv-tech-discuss Digest, Vol 34, Issue 16 > ************************************************** > -- Leopoldo Mauricio Tel: +5521 9 7959-5050
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
