-
Bug
-
Resolution: Done
-
High
-
Casablanca Release
-
OOM with staging docker container (on Windriver lab Integration-OOM-Staging-Daily)
SDNC fails health check after OOM installation. 4 pods can not start.
root@oom-rancher:~# kubectl -n onap get pods | grep sdnc dev-sdnc-controller-blueprints-685488c9dd-nd49j 1/1 Running 0 1h dev-sdnc-controller-blueprints-db-0 1/1 Running 0 1h dev-sdnc-nengdb-0 1/1 Running 0 1h dev-sdnc-network-name-gen-85f85f584-r8v9c 1/1 Running 0 1h dev-sdnc-sdnc-0 2/2 Running 0 1h dev-sdnc-sdnc-1 1/2 Running 0 1h dev-sdnc-sdnc-2 1/2 Running 0 1h dev-sdnc-sdnc-ansible-server-fcc4fbc8-jcrp7 0/1 Init:0/1 7 1h dev-sdnc-sdnc-db-0 2/2 Running 0 1h dev-sdnc-sdnc-dgbuilder-7456f8dbfb-6wsgn 1/1 Running 0 1h dev-sdnc-sdnc-dmaap-listener-665696bff-6hjgt 0/1 Init:0/1 0 1h dev-sdnc-sdnc-portal-846944546c-2zp9h 0/1 Init:0/1 0 1h dev-sdnc-sdnc-ueb-listener-745d7b954f-l82hq 0/1 Init:0/1 0 1h dev-so-so-sdnc-adapter-6f76956969-6lhlh 1/1 Running 0 5h dev-vfc-vfc-zte-sdnc-driver-5f67cb4b9d-7xlgp 1/1 Running 0 5h
Tried redeploy SDNC project, but those 4 pods still don't come up.
20181015:1945 update
all sdnc up on azure as well now
20181015:1930 update michaelobrien
Yang - only 1 container is in pending on my azure
onap onap2-sdnc-ueb-listener-6d685c4557-rnmcb 0/1 Init:0/1 2 56m
and 0 in pending on an AWS standard cluster
onap onap-sdnc-0 2/2 Running 0 1h onap onap-sdnc-ansible-server-dc55dbb6-z6mkc 1/1 Running 0 1h onap onap-sdnc-db-0 2/2 Running 0 1h onap onap-sdnc-dgbuilder-78688789fd-pjj8r 1/1 Running 0 1h onap onap-sdnc-dmaap-listener-b79df77c9-ws6h8 1/1 Running 0 1h onap onap-sdnc-portal-7b779f87f5-pw7px 1/1 Running 0 1h onap onap-sdnc-ueb-listener-5bcdbb8677-xxjgg 1/1 Running 0 1h onap onap-so-sdnc-adapter-76799b95d7-md7nk 1/1 Running 0 1h onap onap-vfc-zte-sdnc-driver-856fc764f5-z8pf7 1/1 Running 0 1h
- relates to
-
LOG-760
20181022 ONAP Academic Summit prep
-
- Closed
-
-
TSC-25 Task Force to implement CD (Continuous Deployment)
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-