-
Bug
-
Resolution: Done
-
Medium
-
None
-
None
-
R3 Sprint 1
See issues with OOM-537 related to the new SDNC-163
17:41:54 5 pending > 0 at the 88th 15 sec interval 17:42:10 onap-aaf aaf-1993711932-934l1 0/1 Running 0 25m 17:42:10 onap-sdnc sdnc-0 0/2 Init:0/1 2 28m 17:42:10 onap-sdnc sdnc-dbhost-0 0/2 Pending 0 28m 17:42:10 onap-sdnc sdnc-dgbuilder-4267203648-kdcrf 0/1 Init:0/1 2 28m 17:42:10 onap-sdnc sdnc-portal-2558294154-j6jx7 0/1 Init:0/1 2 28m
workaround is to restart SDNC on a clean machine
A 2nd createAll will not experience the issue because the docker images were already pulled
Pending (michael) get logs from a clean deployment and add here
- blocks
-
LOG-340 OOM SDNC pod failures starting 1700EDT 20171221 in master - deploy failure on K8S 1.8.4 but not 1.8.6
- Closed
-
OOM-543 SDNC adjust docker pullPolicy to IfNotPresent to speed up initial deployment slowdown introduced by SDNC-163
- Closed
-
SDNC-163 Deploy a SDN-C high availability environment - Kubernetes
- Closed