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

Reply via email to