Sanity Test after deploying VOLTHA

[Kartikeya Verma]

I am getting following Test Scenarios provided by VOLTHA repo . Infact we are not able cleanup ETCD . Any idea why such test case is failing

[Kartikeya Verma]

Updating below the error logs from VOLTHA Test Script (seems image attached not visible). Any idea how to fix this error 

Voltha PODTests :: Test various end-to-end scenarios                  | FAIL |
Suite teardown failed:
Keyword 'Validate Cleanup In ETCD' failed after retrying for 1 minute. The last error was: Several failures occurred:

 

1) Unable to parse pod name

 

2) Stale Devices Data in Etcd!

 

3) Unable to parse pod name

 

4) Stale Flows Data in Etcd!

 

5) Unable to parse pod name

 

6) Stale Logical Devices Data in Etcd!

 

7) Unable to parse pod name

 

8) Stale Logical Flows Data in Etcd!

 

9) Unable to parse pod name
    [ Message content over the limit has been removed. ]

 

13) Unable to parse pod name

 

14) Stale Openolt Data in Etcd!

 

15) Unable to parse pod name

 

16) Stale Openonu Data in Etcd!

 

17) Unable to parse pod name

 

18) Stale Ports Data in Etcd!

 

19) Unable to parse pod name

 

20) Stale Resource Instances Data in Etcd!

 

21) Unable to parse pod name

 

22) Stale Resource Manager Data in Etcd!

 

1 critical test, 0 passed, 1 failed
1 test total, 0 passed, 1 failed

[Stephen Israel]

Hi Kartik

How did you fix this problem? I am getting the same error in my private installation in a Ubuntu server.

Thanks

Stephen Israel

[Kartikeya Verma]

Hi Stephen,

Two things to make Sanity script pass :

1. There shouldn't be any device added in VOLTHA. Just make sure that "voltctl device list" returns NULL

2. Before following https://docs.voltha.org/master/voltha-helm-charts/README.html#running-the-sanity-test-optional, make sure required ports are forwarded and bbsim is installed as suggested in this section using helm. If you already installed bbsim some other way, please delete it and install as suggested in this section.

Hope it may resolve the issue.

Thanks

Kartikeya

[Stephen Israel]

Hi Karthik

Thanks for your suggestion. I have already resolved this problem.

The problem was that the INFRA_NAMESPACE in all the robot scripts was set to "default", but the infra pods (etcd, kafka) were deployed in

the namespace "infra" as documented in the Helm Charts to Deploy VOLTHA 2.x — VOLTHA Docs 2.12.42 documentation.

I changed the INFRA_NAMESPACE to "infra" to resolve this problem.

Regards

Stephen Israel