Hi,

Thanks a lot. Modifying the timer did the trick.

I'd be very glad to help by further testing Danube. But I have to release
the hardware I´ve been using until now. So I don't know where I could
continue testing.

Best regards,

Pau

2017-02-15 17:56 GMT+01:00 Manuel Buil <[email protected]>:

> Hi Pau,
>
> The Colorado release code has a sleep instruction which is executed before
> doing the tests. We wanted to wait for the classifier rules to be
> implemented in ODL:
>
> https://gerrit.opnfv.org/gerrit/gitweb?p=functest.git;
> a=blob;f=testcases/features/sfc/sfc.py;h=90b37b3cf208b55afc80abdf5f9652
> aeabeeb21c;hb=refs/heads/stable/colorado#l503
>
> Unfortunately the code never checked if they were already there (we
> improved this already for OPNFV Danube). As you can see, the sleep is 120
> seconds and your environment takes 197 seconds to update. Try to increase
> that sleep (e.g. 240 seconds) or you can also run the latest OPNFV Danube
> code and help us with the debugging :).
>
> -Manuel
>
>
> On 02/15/2017 04:10 PM, KA PDE wrote:
>
> Hi Manuel,
>
> This is what I get prior to the error:
>
> 2017-02-14 22:12:31,410 - ODL_SFC - INFO - Starting SSH firewall on
> 172.16.0.135
> 2017-02-14 22:12:32,148 - ODL_SFC - INFO - Wait for ODL to update the
> classification rules in OVS
> 2017-02-14 22:14:32,199 - ODL_SFC - INFO - Test SSH
> 2017-02-14 22:14:33,486 - ODL_SFC - INFO - Connection to 11.0.0.4 22 port
> [tcp/ssh] succeeded!
> 2017-02-14 22:14:33,489 - ODL_SFC - ERROR - TEST 1 [FAILED] ==> SSH NOT
> BLOCKED
> 2017-02-14 22:14:34,672 - ODL_SFC - INFO - Test HTTP
> 2017-02-14 22:14:35,081 - ODL_SFC - INFO - Connection to 11.0.0.4 80 port
> [tcp/http] succeeded!
> 2017-02-14 22:14:35,082 - ODL_SFC - INFO - TEST 2 [PASSED] ==> HTTP WORKS
> 2017-02-14 22:14:35,082 - ODL_SFC - INFO - Changing the classification
>
> I'm using a KVM nested deployment. The no-HA scenario which is the only
> one I got to work contains a controller and a pair of compute nodes but all
> the VMs and VNFs are now in a single node.
>
> Now I'm conducting some manual testing to get used to the inner-workings.
> Then maybe I'm able to troubleshooti it further. Will try to migrate them
> between compute nodes and check what happens.
>
> Regards,
>
> Pau
>
> 2017-02-14 19:26 GMT+01:00 Manuel Buil <[email protected]>:
>
>> Hi Pau,
>>
>> It seems like the classifier rules are not in place when doing the first
>> test. Do you get something like this:
>>
>> 2017-02-14 09:19:38,750 - ODL_SFC - INFO - It took 197.696654081 seconds
>>
>> Before your first like "..... INFO - Test SSH"?
>>
>> How many computes are you using? It is the first time I see such a big
>> number of seconds!
>>
>> Thanks,
>> Manuel
>>
>>
>> On 02/14/2017 06:46 PM, KA PDE wrote:
>>
>> Hi Michael, thanks for checking. I've progressed a bit on my side.
>>
>> I'm using matching Fuel and Functest versions. I've been able to test
>> successfully on the non-HA scenario only, though.
>>
>> 2017-02-14 09:19:11,691 - ODL_SFC - INFO - Test SSH
>> 2017-02-14 09:19:12,900 - ODL_SFC - INFO - Connection to 11.0.0.4 22 port
>> [tcp/ssh] succeeded!
>> 2017-02-14 09:19:12,901 - ODL_SFC - ERROR - TEST 1 [FAILED] ==> SSH NOT
>> BLOCKED
>> 2017-02-14 09:19:14,029 - ODL_SFC - INFO - Test HTTP
>> 2017-02-14 09:19:14,603 - ODL_SFC - INFO - Connection to 11.0.0.4 80 port
>> [tcp/http] succeeded!
>> 2017-02-14 09:19:14,604 - ODL_SFC - INFO - TEST 2 [PASSED] ==> HTTP WORKS
>> 2017-02-14 09:19:14,604 - ODL_SFC - INFO - Changing the classification
>> 2017-02-14 09:19:38,750 - ODL_SFC - INFO - It took 197.696654081 seconds
>> 2017-02-14 09:21:07,920 - ODL_SFC - INFO - Test HTTP
>> 2017-02-14 09:21:13,412 - ODL_SFC - INFO - nc: connect to 11.0.0.4 port
>> 80 (tcp) timed out: Operation now in progress
>> 2017-02-14 09:21:13,413 - ODL_SFC - INFO - TEST 3 [PASSED] ==> HTTP
>> Blocked
>> 2017-02-14 09:21:13,413 - ODL_SFC - INFO - Test SSH
>> 2017-02-14 09:21:14,056 - ODL_SFC - INFO - Connection to 11.0.0.4 22 port
>> [tcp/ssh] succeeded!
>> 2017-02-14 09:21:14,057 - ODL_SFC - INFO - TEST 4 [PASSED] ==> SSH Works
>> 2017-02-14 09:21:14,057 - ODL_SFC - ERROR - SFC TESTS: FAIL :( FOUND 1
>> FAIL )
>>
>> I guess this error is minor.
>>
>> Thanks again and best regards,
>>
>> Pau
>>
>> 2017-02-14 11:24 GMT+01:00 Michael Polenchuk <[email protected]>:
>>
>>> Hi,
>>>
>>> We've rechecked it out twice.
>>> With fuel colorado 3.0 iso and functest docker image (tag; colorado.3.0)
>>> we've successful tests run:
>>>   * healthcheck,
>>>   * sdn_suites: ['odl'],
>>>   * features: ['promise', 'odl-sfc']
>>>
>>> I guess you're using latest functest image against fuel colorado iso or
>>> vice versa.
>>>
>>>
>>> On Tue, Feb 14, 2017 at 1:24 AM, KA PDE <[email protected]> wrote:
>>>
>>>> After using the compressed image shared in this list some weeks ago I
>>>> progressed a bit more until...:
>>>>
>>>> +--------------------------------------+----------+---------
>>>> ----+-------------------------------------------------------+--------+
>>>> | id                                   | name     | description |
>>>> acl_match_criteria                                    | status |
>>>> +--------------------------------------+----------+---------
>>>> ----+-------------------------------------------------------+--------+
>>>> | 8b04a3b5-8316-4415-aa04-6c8454ec78a4 | red_ssh  |             |
>>>> {u'source_port': 0, u'protocol': 6, u'dest_port': 22} | ACTIVE |
>>>> | e6e14d65-8adf-4cb9-970f-545c433723c4 | red_http |             |
>>>> {u'source_port': 0, u'protocol': 6, u'dest_port': 80} | ACTIVE |
>>>> +--------------------------------------+----------+---------
>>>> ----+-------------------------------------------------------+--------+
>>>> 2017-02-13 19:40:08,943 - ODL_SFC - INFO - Instance name and ip
>>>> ta-5dfc-2c66-4a4f-b0c9-12378a7a4bf8-vdu1-zpsjpubl5sdu:172.16.0.142
>>>> 2017-02-13 19:40:08,944 - ODL_SFC - INFO - Waiting for instance
>>>> ta-5dfc-2c66-4a4f-b0c9-12378a7a4bf8-vdu1-zpsjpubl5sdu:172.16.0.142 to
>>>> come up
>>>> 2017-02-13 19:40:22,996 - ODL_SFC - INFO - SF:172.16.0.142 is reachable
>>>> 2017-02-13 19:40:33,554 - ODL_SFC - INFO - Instance name and ip
>>>> ta-51fe-96e3-4408-af53-08375bad7bc1-vdu1-bucyl7t4inny:172.16.0.143
>>>> 2017-02-13 19:40:33,554 - ODL_SFC - INFO - Waiting for instance
>>>> ta-51fe-96e3-4408-af53-08375bad7bc1-vdu1-bucyl7t4inny:172.16.0.143 to
>>>> come up
>>>> 2017-02-13 19:40:36,577 - ODL_SFC - INFO - SF:172.16.0.143 is reachable
>>>> 2017-02-13 19:40:42,271 - ODL_SFC - INFO - Instance name and ip
>>>> server:172.16.0.144
>>>> 2017-02-13 19:40:42,271 - ODL_SFC - INFO - Waiting for instance
>>>> server:172.16.0.144 to come up
>>>> 2017-02-13 19:40:46,299 - ODL_SFC - INFO - Server:172.16.0.144 is
>>>> reachable
>>>> 2017-02-13 19:40:53,037 - ODL_SFC - INFO - Instance name and ip
>>>> client:172.16.0.145
>>>> 2017-02-13 19:40:53,037 - ODL_SFC - INFO - Waiting for instance
>>>> client:172.16.0.145 to come up
>>>> 2017-02-13 19:40:59,077 - ODL_SFC - INFO - Client:172.16.0.145 is
>>>> reachable
>>>> 2017-02-13 19:41:08,133 - ODL_SFC - INFO - Instance name and ip
>>>> server:172.16.0.146
>>>> 2017-02-13 19:41:08,133 - ODL_SFC - INFO - Waiting for instance
>>>> server:172.16.0.146 to come up
>>>> 2017-02-13 19:41:16,160 - ODL_SFC - INFO - Server:172.16.0.146 is
>>>> reachable
>>>> Traceback (most recent call last):
>>>>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py",
>>>> line 584, in <module>
>>>>     main()
>>>>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py",
>>>> line 485, in main
>>>>     nova_client, neutron_client)
>>>>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py",
>>>> line 284, in get_floating_ips
>>>>     instance.add_floating_ip(floatip)
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
>>>> line 161, in add_floating_ip
>>>>     return self.manager.add_floating_ip(self, address, fixed_address)
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
>>>> line 883, in add_floating_ip
>>>>     return self._action('addFloatingIp', server, {'address': address})
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
>>>> line 1845, in _action
>>>>     info=info, **kwargs)
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/v2/servers.py",
>>>> line 1856, in _action_return_resp_and_body
>>>>     return self.api.client.post(url, body=body)
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
>>>> line 483, in post
>>>>     return self._cs_request(url, 'POST', **kwargs)
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
>>>> line 458, in _cs_request
>>>>     resp, body = self._time_request(url, method, **kwargs)
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
>>>> line 431, in _time_request
>>>>     resp, body = self.request(url, method, **kwargs)
>>>>   File "/usr/local/lib/python2.7/dist-packages/novaclient/client.py",
>>>> line 425, in request
>>>>     raise exceptions.from_response(resp, body, url, method)
>>>> novaclient.exceptions.BadRequest: No nw_info cache associated with
>>>> instance (HTTP 400) (Request-ID: req-dd67a9f7-a992-4221-b523-89
>>>> 1351ae9b8d)
>>>> Exception in thread Thread-19 (most likely raised during interpreter
>>>> shutdown):Unhandled exception in thread started by <function
>>>> capture_time_log at 0x7f8c6e1d3488>
>>>> Traceback (most recent call last):
>>>>   File "/home/opnfv/repos/functest/testcases/features/sfc/sfc.py",
>>>> line 410, in capture_time_log
>>>>     rsps = ovs_logger.ofctl_time_counter(compute_clients[0])
>>>>   File "/home/opnfv/repos/functest/testcases/features/sfc/ovs_utils.py",
>>>> line 136, in ofctl_time_counter
>>>>     logger.error('Error when countering %s' % e)
>>>> AttributeError: 'NoneType' object has no attribute 'error'
>>>>
>>>> Traceback (most recent call last):
>>>>   File "/usr/lib/python2.7/threading.py", line 810, in
>>>> __bootstrap_inner
>>>>   File "/usr/local/lib/python2.7/dist-packages/paramiko/transport.py",
>>>> line 1777, in run
>>>> <type 'exceptions.AttributeError'>: 'NoneType' object has no attribute
>>>> 'error'
>>>> Collecting python-keystoneclient==3.5.0
>>>>   Using cached python_keystoneclient-3.5.0-py2.py3-none-any.whl
>>>> /usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/
>>>> packages/urllib3/util/ssl_.py:318: SNIMissingWarning: An HTTPS request
>>>> has been made, but the SNI (Subject Name Indication) extension to TLS is
>>>> not available on this platform. This may cause the server to present an
>>>> incorrect TLS certificate, which can cause validation failures. You can
>>>> upgrade to a newer version of Python to solve this. For more information,
>>>> see https://urllib3.readthedocs.io/en/latest/security.html#snimi
>>>> ssingwarning.
>>>>   SNIMissingWarning
>>>> /usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/
>>>> packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true
>>>> SSLContext object is not available. This prevents urllib3 from configuring
>>>> SSL appropriately and may cause certain SSL connections to fail. You can
>>>> upgrade to a newer version of Python to solve this. For more information,
>>>> see https://urllib3.readthedocs.io/en/latest/security.html#insec
>>>> ureplatformwarning.
>>>>   InsecurePlatformWarning
>>>>
>>>> I'm stuck again :\
>>>>
>>>> Any hint will be greatly appreciated.
>>>>
>>>> Regards,
>>>>
>>>> Pau
>>>>
>>>> 2017-02-13 20:16 GMT+01:00 KA PDE <[email protected]>:
>>>>
>>>>> OK. I've been able to progress a little bit until...
>>>>>
>>>>> ...the next error:
>>>>>
>>>>> 2017-02-13 19:03:21,804 - ODL_SFC - INFO - Creating instance
>>>>> 'client'...
>>>>> 2017-02-13 19:07:56,677 - ODL_SFC - INFO - Adding 'client' to security
>>>>> group example-sg
>>>>> 2017-02-13 19:08:00,654 - ODL_SFC - INFO - Creating instance
>>>>> 'server'...
>>>>> 2017-02-13 19:13:42,426 - openstack_utils - ERROR - Timeout booting
>>>>> the instance server.
>>>>> 2017-02-13 19:13:42,427 - ODL_SFC - ERROR - Error while booting
>>>>> instance.
>>>>> Collecting python-keystoneclient==3.5.0
>>>>> /usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/
>>>>> packages/urllib3/util/ssl_.py:318: SNIMissingWarning: An HTTPS
>>>>> request has been made, but the SNI (Subject Name Indication) extension to
>>>>> TLS is not available on this platform. This may cause the server to 
>>>>> present
>>>>> an incorrect TLS certificate, which can cause validation failures. You can
>>>>> upgrade to a newer version of Python to solve this. For more information,
>>>>> see https://urllib3.readthedocs.io/en/latest/security.html#snimi
>>>>> ssingwarning.
>>>>>   SNIMissingWarning
>>>>> /usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/
>>>>> packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true
>>>>> SSLContext object is not available. This prevents urllib3 from configuring
>>>>> SSL appropriately and may cause certain SSL connections to fail. You can
>>>>> upgrade to a newer version of Python to solve this. For more information,
>>>>> see https://urllib3.readthedocs.io/en/latest/security.html#insec
>>>>> ureplatformwarning.
>>>>>   InsecurePlatformWarning
>>>>>
>>>>> This is a nested environment. I'm afraid the resources are not enough.
>>>>>
>>>>> I will try to tweak it or test it manually and report back.
>>>>>
>>>>> Thanks for your time.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Pau
>>>>>
>>>>> 2017-02-13 18:48 GMT+01:00 KA PDE <[email protected]>:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> Well, in fact I am using Fuel in Colorado 3.0, this is why I raised
>>>>>> the issue. And the scenario is ha_odl-l2_sfc_heat_ceilometer_scenario
>>>>>>
>>>>>> Also, do you know if there is something wrong in Colorado 3.0. I'm
>>>>>> getting another error in healthcheck suite:
>>>>>>
>>>>>> healtcheck - ERROR -  The instance opnfv-instance3 couldn't get an IP
>>>>>> from the DHCP agent.
>>>>>>
>>>>>> I'm starting to get frustrated :\
>>>>>>
>>>>>> Thanks and best regards,
>>>>>>
>>>>>> Pau
>>>>>>
>>>>>> 2017-02-13 9:14 GMT+01:00 <[email protected]>:
>>>>>>
>>>>>>> Hi Pau
>>>>>>>
>>>>>>> on which scenario/installer did you try to execute this test?
>>>>>>> according to the dependencies delcared by the SFC team for Colorado
>>>>>>> version (https://git.opnfv.org/functest/tree/ci/testcases.yaml?h=sta
>>>>>>> ble/colorado)
>>>>>>> odl-sfc has the following constraints
>>>>>>>
>>>>>>>                 name: odl-sfc
>>>>>>>                 criteria: 'status == "PASS"'
>>>>>>>                 blocking: false
>>>>>>>                 description: >-
>>>>>>>                     Test suite for odl-sfc to test two chains and two 
>>>>>>> SFs
>>>>>>>                 dependencies:
>>>>>>>                     installer: 'fuel'
>>>>>>>                     scenario: 'odl_l2-sfc'
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> It means that the test is applicable only for Fuel installer  and
>>>>>>> for the specific scenarios including odl_l2-sfc (so in practice
>>>>>>> os-odl_l2-sfc-ha or os-odl_l2-sfc-noha)
>>>>>>> If your configuration is not compatible, you got the type of
>>>>>>> messages you reported
>>>>>>>
>>>>>>> Please note that for Danube, the constraints evolved and apex is now
>>>>>>> compatible (https://git.opnfv.org/functes
>>>>>>> t/tree/functest/ci/testcases.yaml)
>>>>>>>
>>>>>>>                 dependencies:
>>>>>>>                     installer: '(apex)|(fuel)'
>>>>>>>                     scenario: 'odl_l2-sfc'
>>>>>>>
>>>>>>>
>>>>>>> /Morgan
>>>>>>>
>>>>>>>
>>>>>>> Le 13/02/2017 à 04:21, KA PDE a écrit :
>>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> I was giving Functest a try and I'm getting the following error:
>>>>>>>
>>>>>>> /usr/local/lib/python2.7/dist-packages/pip/_vendor/requests/
>>>>>>> packages/urllib3/util/ssl_.py:122: InsecurePlatformWarning: A true
>>>>>>> SSLContext object is not available. This prevents urllib3 from 
>>>>>>> configuring
>>>>>>> SSL appropriately and may cause certain SSL connections to fail. You can
>>>>>>> upgrade to a newer version of Python to solve this. For more 
>>>>>>> information,
>>>>>>> see https://urllib3.readthedocs.io/en/latest/security.html#insec
>>>>>>> ureplatformwarning.
>>>>>>>   InsecurePlatformWarning
>>>>>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known
>>>>>>> hosts.
>>>>>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known
>>>>>>> hosts.
>>>>>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known
>>>>>>> hosts.
>>>>>>> Warning: Permanently added '10.20.0.5' (ECDSA) to the list of known
>>>>>>> hosts.
>>>>>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known
>>>>>>> hosts.
>>>>>>> 2017-02-13 03:15:28,500 - ODL_SFC - INFO - The presetup of the
>>>>>>> server worked
>>>>>>> 2017-02-13 03:15:28,689 - ODL_SFC - INFO - Executing ssh to collect
>>>>>>> the compute IPs
>>>>>>> Warning: Permanently added '10.20.0.2' (ECDSA) to the list of known
>>>>>>> hosts
>>>>>>> (...)
>>>>>>> Warning: Permanently added '10.20.0.6' (ECDSA) to the list of known
>>>>>>> hosts.
>>>>>>> 2017-02-13 03:15:37,096 - ODL_SFC - ERROR - Currently supported only
>>>>>>> Fuel Installer type
>>>>>>>
>>>>>>>             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>>>>>>>
>>>>>>> Could someone provide any hint?
>>>>>>>
>>>>>>> Thanks and best regards,
>>>>>>>
>>>>>>> Pau
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> opnfv-tech-discuss mailing 
>>>>>>> [email protected]https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>>>>>>
>>>>>>> --
>>>>>>> Morgan Richomme
>>>>>>> Orange/ IMT/ OLN/ CNC/ NCA/ SINA
>>>>>>>
>>>>>>> Network architect for innovative services
>>>>>>> Future of the Network community member
>>>>>>> Open source Orange community manager
>>>>>>>
>>>>>>>
>>>>>>> tel. +33 (0) 296 072 106
>>>>>>> mob. +33 (0) 637 753 [email protected]
>>>>>>>
>>>>>>> _________________________________________________________________________________________________________________________
>>>>>>>
>>>>>>> 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.
>>>>>>>
>>>>>>> _______________________________________________ opnfv-tech-discuss
>>>> mailing list [email protected]
>>>> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>>
>>> --
>>>   Michael Polenchuk   Private Cloud / Mirantis Inc.
>>>
>> _______________________________________________
>> opnfv-tech-discuss mailing 
>> [email protected]https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>>
>>
_______________________________________________
opnfv-tech-discuss mailing list
[email protected]
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Reply via email to