Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RC2] [Functest K8s] cnf_testsuite TC failed #3334

Open
sultetveny opened this issue Mar 27, 2023 · 0 comments
Open

[RC2] [Functest K8s] cnf_testsuite TC failed #3334

sultetveny opened this issue Mar 27, 2023 · 0 comments

Comments

@sultetveny
Copy link

I've faced with an issue running the kubernetes cnf test using cnf_testsuite.

podman run -it --env-file ~/opnfv/env \
-v ~/opnfv/ca.pem:/home/opnfv/functest/ca.pem:Z \
-v ~/opnfv/config:/root/.kube/config:Z \
-v ~/opnfv/results:/home/opnfv/functest/results:Z \
-v ~/opnfv/repositories.yml:/home/opnfv/functest/repositories.yml:Z \
-v ~/opnfv/cluster-admin.pem:/home/opnfv/functest/cluster-admin.pem:Z \
-v ~/opnfv/cluster-admin-key.pem:/home/opnfv/functest/cluster-admin-key.pem:Z \
opnfv/functest-kubernetes-cnf:v1.23 /bin/bash

# configure proxy within the container
export https_proxy=http://87.254.212.121:8080
export no_proxy=127.0.0.1,localhost,172.20.110.21

# then within the container
run_tests -t cnf_testsuite

I need to configure the proxy as no direct external access available and it seems, this TC is require it. At least, without the proxy config it failed earlier with this message: "Error connecting to 'github.com:443': Connection refused"

However after proxy configuration it still fails, now with "Index out of bounds". Please check attached logs.
functest-kubernetes.debug.log
functest-kubernetes.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant