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, [email protected] 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" <[email protected]>:
>
>> 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(*(<opnfv.utils.ovs_logger.OVSLogger object at
>> 0x7f32305748d0>, [<opnfv.utils.ssh_utils.ProxyHopClient object at
>> 0x7f3254435790>], 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, [email protected] 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" <[email protected]>:
>>>
>>>> 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, [email protected] 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" <[email protected]>:
>>>>>
>>>>>> 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 <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 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, [email protected]
>>>>>>> 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" <[email protected]>:
>>>>>>>
>>>>>>>> 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 <[email protected]> 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
>>>>>>>>> > > > > > > > <[email protected]> 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-10 at 23:13 +0530, Pavan Gupta wrote:
>>>>>>>>> > > > > Hi Manuel,
>>>>>>>>> > > > > > > > > > Thank you for your reply. We are using Fuel
>>>>>>>>> > > > > > > > > > installer to
>>>>>>>> create a
>>>>>>>>> > > > > > > > > > setup within the company. In addition, we have
>>>>>>>>> > > > > > > > > > access to
>>>>>>>> OPNFV
>>>>>>>>> > > > > > > > > > community lab (Fuel Installer). I can try SFC in the
>>>>>>>> community lab if
>>>>>>>>> > > > > > > > > > things are available. Kindly let me know what needs
>>>>>>>>> > > > > > > > > > to be
>>>>>>>> done.
>>>>>>>>> > > > > Pavan
>>>>>>>>> > > > >
>>>>>>>>> > > > > > > > > > > > > > > > > > On 10-Jul-2017, at 10:56 PM, Manuel
>>>>>>>>> > > > > > > > > > > > > > > > > > Buil <[email protected]>
>>>>>>>> wrote:
>>>>>>>>> > > > > >
>>>>>>>>> > > > > > Hi Pavan,
>>>>>>>>> > > > > >
>>>>>>>>> > > > > > > > > > > > Yes, you can use OPNFV and the SFC project.
>>>>>>>>> > > > > > > > > > > > When would you
>>>>>>>> like to
>>>>>>>>> > > > > > > > > > > > deploy it? We are currently changing the
>>>>>>>>> > > > > > > > > > > > platform and
>>>>>>>> moving from
>>>>>>>>> > > > > > fuel
>>>>>>>>> > > > > > to openstack-ansible, however, we will not be ready before
>>>>>>>>> > > > > > September.
>>>>>>>>> > > > > >
>>>>>>>>> > > > > > Are you familiar with the fuel installer?
>>>>>>>>> > > > > >
>>>>>>>>> > > > > > Regards,
>>>>>>>>> > > > > > Manuel
>>>>>>>>> > > > > >
>>>>>>>>> > > > > > On Mon, 2017-07-10 at 18:23 +0530, Pavan Gupta wrote:
>>>>>>>>> > > > > > > > > > > > > > I am Pavan Gupta from Calsoft Inc., Pune
>>>>>>>>> > > > > > > > > > > > > > (India) and we
>>>>>>>> are
>>>>>>>>> > > > > > > actively
>>>>>>>>> > > > > > > > > > > > > > engaging ourselves with the OPNFV community
>>>>>>>>> > > > > > > > > > > > > > and
>>>>>>>> development
>>>>>>>>> > > > > > > projects.
>>>>>>>>> > > > > > > > > > > > > > As part of this exercise, we are creating
>>>>>>>>> > > > > > > > > > > > > > an OPNFV setup
>>>>>>>> and
>>>>>>>>> > > > > > > would
>>>>>>>>> > > > > > > > > > > > > > like to run sample VNFs and also service
>>>>>>>>> > > > > > > > > > > > > > chain them
>>>>>>>> together. I
>>>>>>>>> > > > > > > would
>>>>>>>>> > > > > > > > > > > > > > like to understand from you if the SFC
>>>>>>>>> > > > > > > > > > > > > > project can be
>>>>>>>> used to
>>>>>>>>> > > > > > > create
>>>>>>>>> > > > > > > a trial NFV system.
>>>>>>>>> > > > > > >
>>>>>>>>> > > > > > > > > > > > > > Also, it would be helpful if you could
>>>>>>>>> > > > > > > > > > > > > > share any
>>>>>>>> documents that
>>>>>>>>> > > > > > > would
>>>>>>>>> > > > > > > help us get started.
>>>>>>>>> > > > > > > Thanking you.
>>>>>>>>> > > > > > > Regards,
>>>>>>>>> > > > > > > Pavan Gupta
>>>>>>>>> > > > >
>>>>>>>>> > > >
>>>>>>>>> > >
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
