Re: [opnfv-tech-discuss] SFC Project
Hi Manuel, Following is the output of the cvs-ofctl command. OFPST_FLOW reply (OF1.3) (xid=0x2): cookie=0x1110010002420255, duration=62656.965s, table=11, n_packets=0, n_bytes=0, tcp, reg0=0x1, tp_dst=80 actions=move:NXM_NX_TUN_ID[0..31]->NXM_NX_NSH_C2[], push_nsh, load:0x1->NXM_NX_NSH_MDTYPE[], load:0x3->NXM_NX_NSH_NP[], load:0xc0a80005->NXM_NX_NSH_C1[], load:0xf2->NXM_NX_NSP[0..23], load:0xff->NXM_NX_NSI[], load:0xb08->NXM_NX_TUN_IPV4_DST[], load:0xf2->NXM_NX_TUN_ID[0..31], resubmit(,0) cookie=0x0, duration=67645.386s, table=11, n_packets=76029, n_bytes=5979053, priority=0 actions=goto_table:21 Pavan > On 19-Jul-2017, at 8:44 PM, Manuel Builwrote: > > ovs-ofctl -O Openflow13 dump-flows br-int table=11 ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] SFC Project
Hi Andres/Manuel, I could run the test cases to completion, however, each one passed partially. I am not sure if the error msgs from neutron log point to subset failure of each test case. Let me know if you have any further pointers. Pavan SFC.log 2017-07-19 11:33:49,911 - __main__ - INFO - Results of test case 'sfc_one_chain_two_service_functions - ODL-SFC Testing SFs when they are located on the same chain': {'status': 'FAIL', 'details': [{'HTTP works': 'PASS'}, {'HTTP not blocked': 'FAIL'}]} 2017-07-19 11:39:17,153 - __main__ - INFO - Results of test case 'sfc_two_chains_SSH_and_HTTP - ODL-SFC tests': {'status': 'FAIL', 'details': [{'SSH Blocked': 'FAIL'}, {'HTTP works': 'PASS'}, {'HTTP Blocked': 'FAIL'}, {'SSH works': 'PASS'}]} 2017-07-19 11:40:57,321 - __main__ - INFO - Results of test case 'sfc_symmetric_chain - Verify the behavior of a symmetric service chain': {'status': 'FAIL', 'details': [{'HTTP works': 'PASS'}, {'HTTP Blocked': 'FAIL'}]} Neutron-all.log 2017-07-19 11:35:17.094 12923 ERROR networking_odl.common.cache Traceback (most recent call last): 2017-07-19 11:35:17.094 12923 ERROR networking_odl.common.cache File "/usr/lib/python2.7/dist-packages/networking_odl/common/cache.py", line 120, in fetch_all 2017-07-19 11:35:17.094 12923 ERROR networking_odl.common.cache for key, value in self._fetch_all(new_entry_keys): 2017-07-19 11:35:17.094 12923 ERROR networking_odl.common.cache File "/usr/lib/python2.7/dist-packages/networking_odl/ml2/network_topology.py", line 228, in _fetch_and_parse_network_topology 2017-07-19 11:35:17.094 12923 ERROR networking_odl.common.cache .format(', '.join(addresses))) 2017-07-19 11:35:17.094 12923 ERROR networking_odl.common.cache ValueError: No such topology element for given host addresses: node-4.domain.tld 2017-07-19 11:35:17.094 12923 ERROR networking_odl.common.cache 2017-07-19T11:35:17.097015+00:00 node-1 neutron-server: 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology [req-960c5cd1-947a-47a6-a2dd-d002dce56176 - - - - -] Network topology element has failed binding port: 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology Traceback (most recent call last): 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology File "/usr/lib/python2.7/dist-packages/networking_odl/ml2/network_topology.py", line 117, in bind_port 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology port_context, vif_type, self._vif_details) 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology File "/usr/lib/python2.7/dist-packages/networking_odl/ml2/ovsdb_topology.py", line 175, in bind_port 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology _('Unable to find any valid segment in given context.')) 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology ValueError: Unable to find any valid segment in given context. 2017-07-19 11:35:17.096 12923 ERROR networking_odl.ml2.network_topology 2017-07-19T11:35:17.097555+00:00 node-1 neutron-server: 2017-07-19 11:35:17.097 12923 ERROR networking_odl.ml2.network_topology [req-960c5cd1-947a-47a6-a2dd-d002dce56176 - - - - -] Unable to bind port element for given host and valid VIF types: 2017-07-19T11:35:17.098497+00:00 node-1 neutron-server: 2017-07-19 11:35:17.098 12923 ERROR neutron.plugins.ml2.managers [req-960c5cd1-947a-47a6-a2dd-d002dce56176 - - - - -] Failed to bind port d09ae072-6b8b-423b-8f07-f562b819ee6c on host node-4.domain.tld for vnic_type normal using segments [{'segmentation_id': None, 'physical_network': u'physnet1', 'id': u'd106fed7-3947-4a29-8506-7841d8a91992', 'network_type': u'flat'}] > On 18-Jul-2017, at 6:31 PM, andres.sanchez.ra...@estudiant.upc.edu wrote: > > Hello Pavan, > > I encountered similar errors in my SFC log, my script also gave an error when > waiting the instance to come up but i have not been able to resolve it. > Looking into your logs I think the problem is in Neutron so you should > probably check Neutron logs, and also validate that you can manually start > instances and assign floating IPs to them. I will let you know if i am able > to resolve my issues. > > Best regards, > > Quoting "Pavan Gupta" <pavan.gu...@calsoftinc.com>: > >> Hi Andres, >> I ran ‘functest openstack clean’ and that tool care of ‘SFC already exist’ >> error. The test ran further till it hit the following issue. In case, you >> have come across this issue, let me know. >> >> >> >> SFC.log >> >> 2017-07-18 08:45:38,445 - ovs_logger - ERROR - list index out of range >> 2017-07-18 08:45:38,447 - sfc.lib.utils - INFO - This is the first_RSP: >> 2017-07-18 08:45:38,589 - ovs_logger - ERROR - list index out of range >> 2017-07-18 08:45:38,590 - sfc.lib.ut
Re: [opnfv-tech-discuss] SFC Project
Hi Andres, I ran ‘functest openstack clean’ and that tool care of ‘SFC already exist’ error. The test ran further till it hit the following issue. In case, you have come across this issue, let me know. SFC.log 2017-07-18 08:45:38,445 - ovs_logger - ERROR - list index out of range 2017-07-18 08:45:38,447 - sfc.lib.utils - INFO - This is the first_RSP: 2017-07-18 08:45:38,589 - ovs_logger - ERROR - list index out of range 2017-07-18 08:45:38,590 - sfc.lib.utils - INFO - These are the rsps: [u'0x24d'] 2017-07-18 08:45:39,592 - sfc.lib.utils - INFO - classification rules updated 2017-07-18 08:45:39,592 - functest_utils - INFO - wait_for_classification_rules(*(, [], 1), **{}) took: 1.26158809662 sec 2017-07-18 08:45:40,972 - sfc.lib.utils - INFO - Instance name and ip ta-1583-7563-4451-9c72-4401f96ca366-vdu1-x5gpjvyrdt6n:172.26.48.61 2017-07-18 08:45:40,973 - sfc.lib.utils - INFO - Waiting for instance ta-1583-7563-4451-9c72-4401f96ca366-vdu1-x5gpjvyrdt6n:172.26.48.61 to come up 2017-07-18 08:47:28,837 - sfc.lib.utils - INFO - Instance ta-1583-7563-4451-9c72-4401f96ca366-vdu1-x5gpjvyrdt6n:172.26.48.61 didn't come up 2017-07-18 08:47:28,837 - __main__ - ERROR - Exception when executing: sfc_one_chain_two_service_functions 2017-07-18 08:47:28,838 - __main__ - ERROR - 'NoneType' object is not iterable Nova Log: 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager [req-0dcc028d-b285-476e-a890-89a13dfd137f e7d3de05afef47ac9ead04257febcb70 517aa5fe041d47ba89b8d90be739e741 - - -] Instance failed network setup after 1 attempt(s) 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager Traceback (most recent call last): 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1401, in _allocate_network_async 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager bind_host_id=bind_host_id) 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 881, in allocate_for_instance 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager bind_host_id, dhcp_opts, available_macs) 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 1000, in _update_ports_for_instance 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager vif.destroy() 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 220, in __exit__ 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager self.force_reraise() 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 196, in force_reraise 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager six.reraise(self.type_, self.value, self.tb) 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 970, in _update_ports_for_instance 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager port_client, instance, port_id, port_req_body) 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 437, in _update_port 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager _ensure_no_port_binding_failure(port) 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager File "/usr/lib/python2.7/dist-packages/nova/network/neutronv2/api.py", line 175, in _ensure_no_port_binding_failure 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager raise exception.PortBindingFailed(port_id=port['id']) 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager PortBindingFailed: Binding failed for port c062c57e-95dc-4c7b-b7a6-0cc003b3a0db, please check neutron logs for more information. 2017-07-18 07:17:33.633 14742 ERROR nova.compute.manager Pavan > On 17-Jul-2017, at 7:14 PM, andres.sanchez.ra...@estudiant.upc.edu wrote: > > Pavan, > > > I have not encountered those errors! It looks like there is already and SFC > classifier already declared, but i thought that if you run the functest > script it deleted anything that was previously declared. Maybe Manuel has any > idea, i am still working on my scenario trying to set it up correctly. > > Best regards, > > Quoting "Pavan Gupta" <pavan.gu...@calsoftinc.com>: > >> HI Andres, >> Thanks to your inputs, the test moved forward, though it failed. Here’s the >> log snippe. Let me know if you know how to fix this issue: >> >> 2017-07-17 12:24:16,434 - tacker_utils - ERROR - error >> [create_sfc(tacker_client, 'red', 'None', '['testVNF1', 'testVNF2']')]: SFC >> with name red already exists!
Re: [opnfv-tech-discuss] SFC Project
HI Andres, Thanks to your inputs, the test moved forward, though it failed. Here’s the log snippe. Let me know if you know how to fix this issue: 2017-07-17 12:24:16,434 - tacker_utils - ERROR - error [create_sfc(tacker_client, 'red', 'None', '['testVNF1', 'testVNF2']')]: SFC with name red already exists! 2017-07-17 12:24:16,463 - tacker_utils - ERROR - error [create_sfc_classifier(tacker_client, 'red_http', 'None','red', '{'source_port': 0, 'protocol': 6, 'dest_port': 80}')]: 'SFC Classifier with name red_http already exists!’ 2017-07-17 12:24:18,094 - ovs_logger - ERROR - list index out of range 2017-07-17 12:24:18,096 - sfc.lib.utils - INFO - This is the first_RSP: 2017-07-17 12:24:18,355 - ovs_logger - ERROR - list index out of range 2017-07-17 12:24:18,356 - sfc.lib.utils - INFO - These are the rsps: [] 2017-07-17 12:24:19,435 - ovs_logger - ERROR - list index out of range 2017-07-17 12:24:19,437 - sfc.lib.utils - INFO - These are the rsps: [] 2017-07-17 12:24:20,262 - sfc.lib.utils - INFO - Instance name and ip ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54 2017-07-17 12:24:20,263 - sfc.lib.utils - INFO - Waiting for instance ta-8503-b3cf-4764-9894-f449e803e904-vdu1-ncexgzd3abmm:172.26.48.54 to come up Pavan > On 17-Jul-2017, at 5:44 PM, andres.sanchez.ra...@estudiant.upc.edu wrote: > > Hello Pavan, > > I encountered a similar problem in my setting, it appears that the problem is > that the configuration file is not updated with your installer IP address. So > what i did was: edit the file > "/home/opnfv/repos/sfc/sfc/tests/functest/config.yaml" and modify the > installer IP address and cluster number. You can get the cluster number by > executing the command "fuel node list" in your Fuel master machine. > > I hope this helps you. > > Best regards, > > Quoting "Pavan Gupta" <pavan.gu...@calsoftinc.com>: > >> HI Andres, >> I now hit issue related to 10.20.0.2 IP address. Though at time of starting >> the container I gave a different IP address, I see there are several files >> that have 10.20.0.2 IP address. Shouldn’t that change? This is where my >> script fails: >> root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log >> 2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out >> Traceback (most recent call last): >> File "./run_tests.py", line 189, in >>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 >> 43, 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 >> 332, in __init__ >>'Cannot establish connection to the installer node!') >> Exception: Cannot establish connection to the installer node! >> >> Pavan >> >>> On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote: >>> >>> Hello Manuel | Pavan, >>> >>> The error where 10.20.0.2 occurs afterwards (when executing functest >>> testcase run odl-sfc), for what I can see this is ocurring at executing >>> "functest env prepare". >>> >>> If I understand correctly this error is indicating that the machine where >>> you are executing the test does not have connectivity to Openstack admin >>> endpoints (which are located in the admin network you set up in Fuel - >>> 192.168.0.0/24 by default). So it is probably a networking configuration >>> issue: you must be either on the same network as openstack admin endpoints >>> (192.168.0.0) or your networking equipment must be able to route packets to >>> this network. In my setup I did not have any problem with iptables so if >>> you are using fuel this is probably not the issue. >>> >>> Best regards, >>> >>> Quoting "Manuel Buil" <mb...@suse.com>: >>> >>>> Andres, can you explain Pavan what you did to solve your issue? I think >>>> he is also hitting the error you found that 10.20.0.2 is hardcoded. >>>> >>>> Thanks, >>>> Manuel >>>> >>>> >>>> On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote: >>>>> > Ok. Any idea what needs to be done. I am trying things at my >>>> side.Pavan >>>>> >>>>> > > > On
Re: [opnfv-tech-discuss] SFC Project
HI Andres, I now hit issue related to 10.20.0.2 IP address. Though at time of starting the container I gave a different IP address, I see there are several files that have 10.20.0.2 IP address. Shouldn’t that change? This is where my script fails: root@c8fc69ea9256:~# cat /home/opnfv/functest/results/sfc.log 2017-07-17 10:40:22,732 - SSH utils - ERROR - timed out Traceback (most recent call last): File "./run_tests.py", line 189, in 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 43, 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 332, in __init__ 'Cannot establish connection to the installer node!') Exception: Cannot establish connection to the installer node! Pavan > On 13-Jul-2017, at 6:35 PM, andres.sanchez.ra...@estudiant.upc.edu wrote: > > Hello Manuel | Pavan, > > The error where 10.20.0.2 occurs afterwards (when executing functest testcase > run odl-sfc), for what I can see this is ocurring at executing "functest env > prepare". > > If I understand correctly this error is indicating that the machine where you > are executing the test does not have connectivity to Openstack admin > endpoints (which are located in the admin network you set up in Fuel - > 192.168.0.0/24 by default). So it is probably a networking configuration > issue: you must be either on the same network as openstack admin endpoints > (192.168.0.0) or your networking equipment must be able to route packets to > this network. In my setup I did not have any problem with iptables so if you > are using fuel this is probably not the issue. > > Best regards, > > Quoting "Manuel Buil" <mb...@suse.com>: > >> Andres, can you explain Pavan what you did to solve your issue? I think >> he is also hitting the error you found that 10.20.0.2 is hardcoded. >> >> Thanks, >> Manuel >> >> >> On Thu, 2017-07-13 at 15:28 +0530, Pavan Gupta wrote: >>> > Ok. Any idea what needs to be done. I am trying things at my >> side.Pavan >>> >>> > > > On 12-Jul-2017, at 7:32 PM, Manuel Buil <mb...@suse.com> wrote: >>> > Hey Pavan, >>> > >>> > > > > > The container must be able to contact the openstack environment, >> otherwise it cannot trigger openstack actions. Do you have perhaps >> a problem with iptables? >>> > >>> > Regards, >>> > Manuel >>> > On Wed, 2017-07-12 at 19:05 +0530, Pavan Gupta wrote: >>> > > Hi Manuel, >>> > > > > > I have deployed the setup for SFC Functest now. However, while >> preparing the environment, I see the following error: >>> > > >>> > > >>> > > > > > 2017-07-12 13:31:30,091 - prepare_env - INFO - >>Verifying >> connectivity to the admin endpoint 192.168.0.2:35357... >>> > > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - ERROR: Cannot >> talk to the admin endpoint 192.168.0.2:35357 . >>> > > > > > 2017-07-12 13:33:20,236 - prepare_env - ERROR - Problem while >> running 'check_os.sh'. >>> > > > > > > > > 2017-07-12 13:33:20,299 - functest_utils - ERROR - The >>> > > > > > > > > command >> 'python /home/opnfv/repos/functest/functest/ci/prepare_env.py >> start' failed. >>> > > >>> > > >>> > > > > > In case, you know if there is a fix for this issue, kindly let me >> know. >>> > > Thanking you. >>> > > Regards, >>> > > Pavan >>> > > >>> > > >>> > > > > > > > On 11-Jul-2017, at 1:20 PM, Manuel Buil <mb...@suse.com> >>> > > > > > > > wrote: >>> > > > Hello, >>> > > > >>> > > > > > > > Ok, if you are familiar with the fuel installer, then follow >> this >>> > > > guide: >>> > > > >>> > > > > > > > https://wiki.opnfv.org/display/sfc/OPNFV-SFC+Functest+test+case >> s >>> > > > >>> > > > Regards, >>> > > > Manuel >>> > > > >>> > > > On Mon, 2017-07-
Re: [opnfv-tech-discuss] SFC Project
Ok. Not sure Manuel how to get tacker file. Do you have any ideas or suggestions? I am quite new to openstack in general. Pavan > On 14-Jul-2017, at 7:35 PM, Manuel Builwrote: > > tackerc file not found, fetching it from controller ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] SFC Project
HI Manuel, Tacker was deployed in the beginning itself. Please check the attached image. Is there anything else I need to deploy Tacker? Pavan > On 14-Jul-2017, at 7:07 PM, Manuel Buil <mb...@suse.com> wrote: > > Hello Pavan, > > In the logs you sent previously, that step worked but it was not able to > fetch tackerc. Did you deploy your environment activating tacker? It should > be under settings > openstack services. > > -Manuel > > On Fri, 2017-07-14 at 18:36 +0530, Pavan Gupta wrote: >> HI Jose, >> This is sfc.log >> >> >> 2017-07-14 12:57:13,258 - SSH utils - ERROR - timed out >> 2017-07-14 12:58:13,319 - SSH utils - ERROR - timed out >> 2017-07-14 12:59:13,348 - SSH utils - ERROR - timed out >> 2017-07-14 13:00:13,405 - SSH utils - ERROR - timed out >> 2017-07-14 13:00:13,406 - __main__ - INFO - Fetch /etc/heat/heat.conf from >> controller 10.192.3.70 >> 2017-07-14 13:00:13,406 - opnfv.deployment.manager - INFO - Fetching >> /etc/heat/heat.conf from 10.192.3.70 >> 2017-07-14 13:00:13,406 - SSH utils - ERROR - Error [get_file(ssh_conn, >> '/etc/heat/heat.conf', '/tmp/heat.conf']: 'NoneType' object has no attribute >> 'open_sftp' >> 2017-07-14 13:00:13,406 - opnfv.deployment.manager - ERROR - SFTP failed to >> retrieve the file. >> 2017-07-14 13:00:13,407 - __main__ - INFO - Replace /etc/heat/heat.conf with >> /tmp/heat.conf in controller 10.192.3.70 >> 10.20.0.2 >> root >> r00tme >> None >> --*-* >> Installer Connection = >> Traceback (most recent call last): >> File "./run_tests.py", line 189, in >> main(report=args.report) >> File "./run_tests.py", line 91, in main >> disable_heat_resource_finder_cache(nodes) >> File "./run_tests.py", line 67, in disable_heat_resource_finder_cache >> controller.run_cmd('rm -f {0}'.format(remote_heat_conf)) >> File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line >> 184, in run_cmd >> _, stdout, stderr = (self.ssh_client.exec_command(cmd)) >> AttributeError: 'NoneType' object has no attribute ‘exec_command' >> >> >> Pavan >> >> >>> On 14-Jul-2017, at 6:32 PM, Jose Lausuch <jose.laus...@ericsson.com >>> <mailto:jose.laus...@ericsson.com>> wrote: >>> >>> Hi, >>> >>> Functest looks fine. Can you now attach sfc.log located in the same >>> directory? Maybe it’s a problem with the test case as such while trying to >>> access the deployment. Maybe Manuel has more experience with it. >>> >>> - Jose - >>> >>> >>>> On 14 Jul 2017, at 14:47, Pavan Gupta <pavan.gu...@calsoftinc.com >>>> <mailto:pavan.gu...@calsoftinc.com>> wrote: >>>> >>>> HI Jose, >>>> - I have attached the log file this time. >>>> >>>> - Output of docker images: >>>> >>>> REPOSITORY TAG IMAGE ID >>>> CREATED SIZE >>>> opnfv/functest stable 2553087919e09 days >>>> ago 1.57GB >>>> ryu7249125/yardsticklatest e37ee4c07ca82 >>>> months ago3.52GB >>>> opnfv/yardstick stable 7fc31a6fc1d52 >>>> months ago1.2GB >>>> autolytiks_logstash latest 0b8f850cf5922 >>>> months ago565MB >>>> autolytiks_elasticsearchlatest f73bc006eb572 >>>> months ago352MB >>>> autolytiks_nginxlatest b3d688b354172 >>>> months ago206MB >>>> autolytiks_web latest 7c2907bd15d82 >>>> months ago727MB >>>> python 3.5-onbuild 2d1685b88f322 >>>> months ago689MB >>>> redis latest e32ef7250bc12 >>>> months ago184MB >>>> postgreslatest 3902208677552 >>>> months ago267MB >>>> influxdblatest 95b868946bae2 >>>> months ago224MB >>>> logstash5.2 e2e0c054df393 >>>> months ago494
Re: [opnfv-tech-discuss] SFC Project
HI Jose, This is sfc.log 2017-07-14 12:57:13,258 - SSH utils - ERROR - timed out 2017-07-14 12:58:13,319 - SSH utils - ERROR - timed out 2017-07-14 12:59:13,348 - SSH utils - ERROR - timed out 2017-07-14 13:00:13,405 - SSH utils - ERROR - timed out 2017-07-14 13:00:13,406 - __main__ - INFO - Fetch /etc/heat/heat.conf from controller 10.192.3.70 2017-07-14 13:00:13,406 - opnfv.deployment.manager - INFO - Fetching /etc/heat/heat.conf from 10.192.3.70 2017-07-14 13:00:13,406 - SSH utils - ERROR - Error [get_file(ssh_conn, '/etc/heat/heat.conf', '/tmp/heat.conf']: 'NoneType' object has no attribute 'open_sftp' 2017-07-14 13:00:13,406 - opnfv.deployment.manager - ERROR - SFTP failed to retrieve the file. 2017-07-14 13:00:13,407 - __main__ - INFO - Replace /etc/heat/heat.conf with /tmp/heat.conf in controller 10.192.3.70 10.20.0.2 root r00tme None --*-* Installer Connection = Traceback (most recent call last): File "./run_tests.py", line 189, in main(report=args.report) File "./run_tests.py", line 91, in main disable_heat_resource_finder_cache(nodes) File "./run_tests.py", line 67, in disable_heat_resource_finder_cache controller.run_cmd('rm -f {0}'.format(remote_heat_conf)) File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 184, in run_cmd _, stdout, stderr = (self.ssh_client.exec_command(cmd)) AttributeError: 'NoneType' object has no attribute ‘exec_command' Pavan > On 14-Jul-2017, at 6:32 PM, Jose Lausuch <jose.laus...@ericsson.com> wrote: > > Hi, > > Functest looks fine. Can you now attach sfc.log located in the same > directory? Maybe it’s a problem with the test case as such while trying to > access the deployment. Maybe Manuel has more experience with it. > > - Jose - > > >> On 14 Jul 2017, at 14:47, Pavan Gupta <pavan.gu...@calsoftinc.com >> <mailto:pavan.gu...@calsoftinc.com>> wrote: >> >> HI Jose, >> - I have attached the log file this time. >> >> - Output of docker images: >> >> REPOSITORY TAG IMAGE IDCREATED >>SIZE >> opnfv/functest stable 2553087919e09 days >> ago 1.57GB >> ryu7249125/yardsticklatest e37ee4c07ca82 months >> ago3.52GB >> opnfv/yardstick stable 7fc31a6fc1d52 months >> ago1.2GB >> autolytiks_logstash latest 0b8f850cf5922 months >> ago565MB >> autolytiks_elasticsearchlatest f73bc006eb572 months >> ago352MB >> autolytiks_nginxlatest b3d688b354172 months >> ago206MB >> autolytiks_web latest 7c2907bd15d82 months >> ago727MB >> python 3.5-onbuild 2d1685b88f322 months >> ago689MB >> redis latest e32ef7250bc12 months >> ago184MB >> postgreslatest 3902208677552 months >> ago267MB >> influxdblatest 95b868946bae2 months >> ago224MB >> logstash5.2 e2e0c054df393 months >> ago494MB >> elasticsearch 5.2 0206b7302cfe3 months >> ago352MB >> grafana/grafana latest 8c4ef64b4ad13 months >> ago278MB >> autolytiks_kibana latest 724639b709153 months >> ago329MB >> kibana 5.2 724639b709153 months >> ago329MB >> hello-world latest c54a2cc56cbb12 >> months ago 1.85kB >> opennetworklinux/builder7 1.2 a0a471ea8d5513 >> months ago 1.92GB >> tutum/nginx latest a2e9b71ed36616 >> months ago 206MB >> >> >> - Output of docker ps: >> CONTAINER IDIMAGECOMMAND >> CREATED STATUS PORTS >> NAMES >> 9b1c47899d65opnfv/functest:stable"/bin/bash" 6 >> hours ago Up 6 hours >> sfc >> 0eb2d3ff7e4dautolytiks_nginx
Re: [opnfv-tech-discuss] SFC Project
Hi Jose, 1. I have attached functest.log. 2. Docker image: Docker version 17.04.0-ce, build 4845c56 3. Installer: Fuel, version 10.0.0 4. Credentials: Same as mentioned in the link (root, r00tme) Thank you. Pavan > On 14-Jul-2017, at 5:15 PM, Jose Lausuchwrote: > > /home/opnfv/functest/results/functest.log ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] SFC Project
Hi Manuel, - I am using funkiest command list. I run this command: 'functest testcase run odl-sfc’ - I am new openstack as well, can you please tell me, what all env variables need to be set. Do I need to copy these in openstack.creds. This is what is there at present in this file: OS_REGION_NAME=RegionOne OS_DEFAULT_DOMAIN=default OS_USER_DOMAIN_NAME=Default OS_PROJECT_NAME=admin OS_IDENTITY_API_VERSION=3 OS_PASSWORD=admin OS_AUTH_STRATEGY=keystone OS_AUTH_URL=http://192.168.0.2:5000/ <http://192.168.0.2:5000/> OS_USERNAME=admin OS_TENANT_NAME=admin OS_ENDPOINT_TYPE=internalURL OS_NO_CACHE=true OS_PROJECT_DOMAIN_NAME=Default - Where do I run ‘openstack server list’ command. I tried running it on node-1 machine, which is a controller machine, the output was blank. Any useful pointer would be appreciated. Pavan - > On 14-Jul-2017, at 4:49 PM, Manuel Buil <mb...@suse.com> wrote: > > HI Pavan, > > I think your openstack env. variables are not set. How do you execute the > tests? > > If you are not using the functest command line, you need to source the env > variables (from openrc or tackerc). To check that everything is ok, try to > execute one openstack command before executing the test and check that you > don't get any error (e.g. openstack server list). > > Regards, > Manuel > > On Fri, 2017-07-14 at 16:40 +0530, Pavan Gupta wrote: >> Hello Folks, >> I have managed to begin the test but hit across this error: >> >> Traceback (most recent call last): >> File "./run_tests.py", line 189, in >> main(report=args.report) >> File "./run_tests.py", line 91, in main >> disable_heat_resource_finder_cache(nodes) >> File "./run_tests.py", line 67, in disable_heat_resource_finder_cache >> controller.run_cmd('rm -f {0}'.format(remote_heat_conf)) >> File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line >> 184, in run_cmd >> _, stdout, stderr = (self.ssh_client.exec_command(cmd)) >> AttributeError: 'NoneType' object has no attribute ‘exec_command' >> >> >> Does anyone know fix for this? >> Pavan >> >>> On 14-Jul-2017, at 12:56 PM, Jose Lausuch <jose.laus...@ericsson.com >>> <mailto:jose.laus...@ericsson.com>> wrote: >>> >>> Ok, just for your information: >>> if you are using Functest Danube, you need connectivity to the admin >>> network. We are working on removing that constraint in Euphrates against >>> OpenStack Ocata. >>> >>> Thanks, >>> Jose >>> >>> >>> >>>> On 14 Jul 2017, at 08:45, Pavan Gupta <pavan.gu...@calsoftinc.com >>>> <mailto:pavan.gu...@calsoftinc.com>> wrote: >>>> >>>> Hi Jose, >>>> I added the following route on Junper host and connectivity worked, so the >>>> SFC test environment was successfully prepared. >>>> sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23 >>>> >>>> Thanks for your help. >>>> Pavan >>>> >>>>> On 13-Jul-2017, at 7:06 PM, Jose Lausuch <jose.laus...@ericsson.com >>>>> <mailto:jose.laus...@ericsson.com>> wrote: >>>>> >>>>> Hi Pavan, >>>>> >>>>> It seems your installer is not supported by the script fetch_os_creds.sh >>>>> >>>>> In that case, you need to provide the openstack RC file from your >>>>> deployment manually to the container, or just copy the content to >>>>> /home/opnfv/functest/conf/openstack.creds >>>>> >>>>> Let me know if it still fails that way. >>>>> >>>>> Regards, >>>>> Jose >>>>> >>>>> >>>>> From: opnfv-tech-discuss-boun...@lists.opnfv.org >>>>> <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> >>>>> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org >>>>> <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>] On Behalf Of Pavan >>>>> Gupta >>>>> Sent: Thursday, July 13, 2017 14:29 PM >>>>> To: Manuel Buil <mb...@suse.com <mailto:mb...@suse.com>> >>>>> Cc: andres.sanchez.ra...@estudiant.upc.edu >>>>> <mailto:andres.sanchez.ra...@estudiant.upc.edu>; OPNFV-TECH-DISCUSS OPNFV >>>>> <opnfv-tech-discuss@lists.opnfv.org >>>>> <mailto:opnfv-tech-discuss@lists.opnfv.org>> >>>>> Subject: Re: [opnfv-tech-discuss] SFC Project >>>>> >>>>> Hi Manuel/Andres, >>>>> When I run 'functest env prepare’, I also see this issue: >>>>> >>>>> >>>>> /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: >>>>> SALT_MASTER_IP: unbound variable >>>>> >>>>> What should be SALT_MASTER_IP address? >>>>> Pavan >>>>> >>>>> On 13-Jul-2017, at 3:37 PM, Manuel Buil <mb...@suse.com >>>>> <mailto:mb...@suse.com>> wrote: >>>>> >>>>> 10.20.0.2 >>>> >>> >> ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] SFC Project
Hello Folks, I have managed to begin the test but hit across this error: Traceback (most recent call last): File "./run_tests.py", line 189, in main(report=args.report) File "./run_tests.py", line 91, in main disable_heat_resource_finder_cache(nodes) File "./run_tests.py", line 67, in disable_heat_resource_finder_cache controller.run_cmd('rm -f {0}'.format(remote_heat_conf)) File "/home/opnfv/repos/releng/modules/opnfv/deployment/manager.py", line 184, in run_cmd _, stdout, stderr = (self.ssh_client.exec_command(cmd)) AttributeError: 'NoneType' object has no attribute ‘exec_command' Does anyone know fix for this? Pavan > On 14-Jul-2017, at 12:56 PM, Jose Lausuch <jose.laus...@ericsson.com> wrote: > > Ok, just for your information: > if you are using Functest Danube, you need connectivity to the admin network. > We are working on removing that constraint in Euphrates against OpenStack > Ocata. > > Thanks, > Jose > > > >> On 14 Jul 2017, at 08:45, Pavan Gupta <pavan.gu...@calsoftinc.com >> <mailto:pavan.gu...@calsoftinc.com>> wrote: >> >> Hi Jose, >> I added the following route on Junper host and connectivity worked, so the >> SFC test environment was successfully prepared. >> sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23 >> >> Thanks for your help. >> Pavan >> >>> On 13-Jul-2017, at 7:06 PM, Jose Lausuch <jose.laus...@ericsson.com >>> <mailto:jose.laus...@ericsson.com>> wrote: >>> >>> Hi Pavan, >>> >>> It seems your installer is not supported by the script fetch_os_creds.sh >>> >>> In that case, you need to provide the openstack RC file from your >>> deployment manually to the container, or just copy the content to >>> /home/opnfv/functest/conf/openstack.creds >>> >>> Let me know if it still fails that way. >>> >>> Regards, >>> Jose >>> >>> >>> From: opnfv-tech-discuss-boun...@lists.opnfv.org >>> <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org> >>> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org >>> <mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>] On Behalf Of Pavan >>> Gupta >>> Sent: Thursday, July 13, 2017 14:29 PM >>> To: Manuel Buil <mb...@suse.com <mailto:mb...@suse.com>> >>> Cc: andres.sanchez.ra...@estudiant.upc.edu >>> <mailto:andres.sanchez.ra...@estudiant.upc.edu>; OPNFV-TECH-DISCUSS OPNFV >>> <opnfv-tech-discuss@lists.opnfv.org >>> <mailto:opnfv-tech-discuss@lists.opnfv.org>> >>> Subject: Re: [opnfv-tech-discuss] SFC Project >>> >>> Hi Manuel/Andres, >>> When I run 'functest env prepare’, I also see this issue: >>> >>> >>> /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: SALT_MASTER_IP: >>> unbound variable >>> >>> What should be SALT_MASTER_IP address? >>> Pavan >>> >>> On 13-Jul-2017, at 3:37 PM, Manuel Buil <mb...@suse.com >>> <mailto:mb...@suse.com>> wrote: >>> >>> 10.20.0.2 >> > ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] SFC Project
Hi Jose, - I run the docker within Jumphost machine. - I have put the following content in openstack.creds file: OS_REGION_NAME=RegionOne OS_DEFAULT_DOMAIN=default OS_USER_DOMAIN_NAME=Default OS_PROJECT_NAME=admin OS_IDENTITY_API_VERSION=3 OS_PASSWORD=admin OS_AUTH_STRATEGY=keystone OS_AUTH_URL=http://192.168.0.2:5000/ OS_USERNAME=admin OS_TENANT_NAME=admin OS_ENDPOINT_TYPE=internalURL OS_NO_CACHE=true OS_PROJECT_DOMAIN_NAME=Default - IP address 192.168.0.2 isn’t accessible for the docker and the Jumphost. If I give public IP address, then the connectivity works. Is it possible to use public ip addresses and get the test going? Pavan > On 13-Jul-2017, at 7:06 PM, Jose Lausuchwrote: > > /home/opnfv/functest/conf/openstack.creds ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] SFC Project
Hi Jose, I added the following route on Junper host and connectivity worked, so the SFC test environment was successfully prepared. sudo route add -net 192.168.0.0 netmask 255.255.255.0 gw 172.26.48.23 Thanks for your help. Pavan > On 13-Jul-2017, at 7:06 PM, Jose Lausuch <jose.laus...@ericsson.com> wrote: > > Hi Pavan, > > It seems your installer is not supported by the script fetch_os_creds.sh > > In that case, you need to provide the openstack RC file from your deployment > manually to the container, or just copy the content to > /home/opnfv/functest/conf/openstack.creds > > Let me know if it still fails that way. > > Regards, > Jose > > > From: opnfv-tech-discuss-boun...@lists.opnfv.org > [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Pavan Gupta > Sent: Thursday, July 13, 2017 14:29 PM > To: Manuel Buil <mb...@suse.com> > Cc: andres.sanchez.ra...@estudiant.upc.edu; OPNFV-TECH-DISCUSS OPNFV > <opnfv-tech-discuss@lists.opnfv.org> > Subject: Re: [opnfv-tech-discuss] SFC Project > > Hi Manuel/Andres, > When I run 'functest env prepare’, I also see this issue: > > > /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: SALT_MASTER_IP: > unbound variable > > What should be SALT_MASTER_IP address? > Pavan > > On 13-Jul-2017, at 3:37 PM, Manuel Buil <mb...@suse.com > <mailto:mb...@suse.com>> wrote: > > 10.20.0.2 ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
Re: [opnfv-tech-discuss] SFC Project
Hi Manuel/Andres, When I run 'functest env prepare’, I also see this issue: /home/opnfv/repos/releng/utils/fetch_os_creds.sh: line 76: SALT_MASTER_IP: unbound variable What should be SALT_MASTER_IP address? Pavan > On 13-Jul-2017, at 3:37 PM, Manuel Builwrote: > > 10.20.0.2 ___ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss