📞📱☎️📡🌐 Cloud Native Telecom Initiative (CNTI) Test Catalog is a tool to check for and provide feedback on the use of K8s + cloud native best practices in networking applications and platforms
Describe the bug
NSM example is not working when cnf_setup is called. I see there few issues.
It is failing on:
Helm install error: Chart.yaml file is missing
I think that this issue is caused by incorrect release_name in cnf-testsuite.yml. Where is something weird:
release_name: nsm --set insecure=true.
I tried it to run it with just release_name: nsm and then new issues popped up.
Issues after fixed incorrect release_name and rerun of cnf_setup:
Helm installation failedHelm install error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind"CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1", unable to recognize "": no matches for kind `"MutatingWebhookConfiguration" in version "admissionregistration.k8s.io/v1beta1"]``
Which I think is caused by using a newer version of Kubernetes. But I tested it with v1.23.13, which is not one of the recent ones. So I suggest updating this nsm example to be able to work with newer versions of Kubernetes
To Reproduce
./cnf-testsuite cnf_setup cnf-config=example-cnfs/nsm/cnf-testsuite.yml
Expected behavior
CNF setup should pass without issues and nsm cnf has to be in running state.
Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):
cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
Describe the bug NSM example is not working when cnf_setup is called. I see there few issues.
Helm install error: Chart.yaml file is missing
I think that this issue is caused by incorrect
release_name
incnf-testsuite.yml
. Where is something weird:release_name: nsm --set insecure=true
. I tried it to run it with justrelease_name: nsm
and then new issues popped up.Helm installation failed
Helm install error: unable to build kubernetes objects from release manifest: [unable to recognize "": no matches for kind
"CustomResourceDefinition" in version "apiextensions.k8s.io/v1beta1", unable to recognize "": no matches for kind
`"MutatingWebhookConfiguration" in version "admissionregistration.k8s.io/v1beta1"]``Which I think is caused by using a newer version of Kubernetes. But I tested it with v1.23.13, which is not one of the recent ones. So I suggest updating this nsm example to be able to work with newer versions of Kubernetes
To Reproduce ./cnf-testsuite cnf_setup cnf-config=example-cnfs/nsm/cnf-testsuite.yml
Expected behavior CNF setup should pass without issues and nsm cnf has to be in running state.
Screenshots If applicable, add screenshots to help explain your problem.
Device (please complete the following information): cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04.3 LTS"
kubectl version Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.13", GitCommit:"592eca05be27f7d927d0b25cbb4241d75a9574bf", GitTreeState:"clean", BuildDate:"2022-10-12T10:57:16Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"} Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.13", GitCommit:"592eca05be27f7d927d0b25cbb4241d75a9574bf", GitTreeState:"clean", BuildDate:"2022-10-12T10:50:48Z", GoVersion:"go1.17.13", Compiler:"gc", Platform:"linux/amd64"}
How will this be tested? aka Acceptance Criteria (optional)
Create new nsm cnf with cnf_setup command and it has to pass and correctly create new cnf.