-
Bug
-
Resolution: Done
-
High
-
Honolulu Release
-
None
When deploying `onap/cps-and-nf-proxy:0.0.1`, `cps` container is not starting because `cps-readiness` init container is terminating in error with :
Traceback (most recent call last): File "/app/ready.py", line 33, in <module> from kubernetes import client ModuleNotFoundError: No module named 'kubernetes'
Init Containers: cps-readiness: Container ID: docker://b6509714992a2ff04eaa35d90282abb4087d02dc785ec223a7043f9e0a540b50 Image: registry-public.nso.lab-services.ca/onap/oom/readiness:3.0.1 Image ID: docker-pullable://nexus3.onap.org:10001/onap/oom/readiness@sha256:317c8a361ae73750f4d4a1b682c42b73de39083f73228dede31fd68b16c089db Port: <none> Host Port: <none> Command: /app/ready.py Args: --container-name cps-postgres State: Waiting Reason: CrashLoopBackOff Last State: Terminated Reason: Error Exit Code: 1 Started: Wed, 24 Feb 2021 11:23:11 -0500 Finished: Wed, 24 Feb 2021 11:23:15 -0500 Ready: False Restart Count: 177 Limits: cpu: 100m memory: 100Mi Requests: cpu: 3m memory: 100Mi Environment: NAMESPACE: rockhoppers (v1:metadata.namespace) Mounts: /var/run/secrets/kubernetes.io/serviceaccount from bison-cps-read-token-cfrvt (ro)
This error occurs in both Bell and Nordix dev envs.
- blocks
-
CPS-175 Deploy CPS & Postgress DB images as part of ONAP install
- Closed