-
Bug
-
Resolution: Done
-
Highest
-
Dublin Release
-
None
-
Integration-OOM-Staging-Daily
After ONAP deployment, SDNC pod doesn't come up successfully
root@staging-rancher:~# kubectl -n onap get pod |grep sdnc- dev-sdnc-cds-blueprints-processor-5945f5695d-vfmsb 1/1 Running 13 6h dev-sdnc-cds-command-executor-54dff699f-2gb2n 1/1 Running 0 6h dev-sdnc-cds-controller-blueprints-5d966b47-5mmfr 1/1 Running 1 6h dev-sdnc-cds-db-0 1/1 Running 0 6h dev-sdnc-cds-ui-85cc9c9b47-mrcxm 1/1 Running 0 6h dev-sdnc-nengdb-0 1/1 Running 0 6h dev-sdnc-network-name-gen-6b6cdc7476-x5m9m 1/1 Running 0 6h dev-sdnc-sdnc-0 1/2 Running 0 6h dev-sdnc-sdnc-ansible-server-67d8cb8756-fvxp7 0/1 Init:0/1 35 6h dev-sdnc-sdnc-dgbuilder-66489bbc79-rqhpj 1/1 Running 0 6h dev-sdnc-sdnc-dmaap-listener-dd4865868-mxtgc 0/1 Init:0/1 0 6h dev-sdnc-sdnc-ueb-listener-6c76876f94-dnznz 0/1 Init:0/1 0 6h
sdnc-sdnc-0 console log is attached. They are a couple noticeable errors in the log. 1) db error at the top of the log. 2) file permission denied error near the bottom of the log