SUMMARY
I enable network-name-generator in SDNC values, deploy SDNC but network-name-generator doesn't work
OS / ENVIRONMENT
- Kubernetes version:
Server Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.9", GitCommit:"9dd794e454ac32d97cde41ae10be801ae98f75df", GitTreeState:"clean", BuildDate:"2021-03-18T01:00:06Z", GoVersion:"go1.15.8", Compiler:"gc", Platform:"linux/amd64"}
- Helm version:
v3.5.3+g041ce5a
- Kubernetes mode of installation:
<!-- add also configuration file if relevant -->
<!-- please run:
docker run -e DEPLOY_SCENARIO=k8s-test \
-v <the kube config>:/root/.kube/config \
opnfv/functest-kubernetes-healthcheck:latest
-->
<!-- and upload the result directory as a zip file -->
- CNI Used for Kubernetes:
- type of installation:
NAME STATUS ROLES AGE VERSION
integration-master-0 Ready controlplane,etcd 58d v1.19.9
integration-master-1 Ready controlplane,etcd 58d v1.19.9
integration-master-2 Ready controlplane,etcd 58d v1.19.9
integration-node-0 Ready worker 58d v1.19.9
integration-node-1 Ready worker 58d v1.19.9
integration-node-2 Ready worker 58d v1.19.9
integration-node-3 Ready worker 58d v1.19.9
integration-node-4 Ready worker 58d v1.19.9
integration-node-5 Ready worker 58d v1.19.9
integration-node-6 Ready worker 58d v1.19.9
integration-node-7 Ready worker 58d v1.19.9
OOM VERSION
Branch: honolulu
CONFIGURATION
Will be attached
STEPS TO REPRODUCE
- helm dep up && {{helm package }}.
- helm upgrade sdnc moveon/sdnc --install --namespace onap -f onap.yaml -f sdnc.yaml --debug
EXPECTED RESULTS
sdnc-network-name-gen deployment creates sdnc-network-name-gen-bla-bla pod which is running, sdnc-nengdb-init-config-job create a pod which completes without errors
ACTUAL RESULTS **
- sdnc-nengdb-init-config-job pod fails due to invalid secret name is generated
- name: MYSQL_ROOT_PASSWORD
valueFrom:
secretKeyRef:
key: password
name: sdnc-sdnc-db-db-root-password
Value sdnc-sdnc-db-db-root-password doesn't exist, it should be sdnc-sdnc-db-root-password
- sdnc-network-name-gen-7b5746768b-g5q98's initContainer network-name-gen-readiness hangs due to container it checks doesn't exist
Command:
/app/ready.py
Args:
--container-name
nangdb
nangdb container doesn't exists, it should check sdnc-nengdb-init-config-job-k69d7 status
- sdnc-network-name-gen-7b5746768b-g5q98's container network-name-gen tries has invalid NENG_DB_URL value
NENG_DB_URL: jdbc:mysql://nengdb:/nengdb
but it should be
NENG_DB_URL: jdbc:mysql://sdnc-db:3306/nengdb
With the fixes I wrote above it works