-
Bug
-
Resolution: Done
-
Medium
-
Beijing Release
See pending containers in the latest deployment
http://jenkins.onap.info/job/oom-cd-master/2970/console
4:02:38 pending containers=3 14:02:38 onap onap-aai-champ-85f97f5d7c-gdwbx 0/1 Running 0 1h 14:02:38 onap onap-dcae-redis-3 0/1 CrashLoopBackOff 25 1h 14:02:38 onap onap-uui-server-78b6bf799b-2dlh7 0/1 CrashLoopBackOff 31 1h
Healthcheck is actually at the start of the next run
http://jenkins.onap.info/job/oom-cd-master/2971/consoleFull
16:00:12 Basic UseCaseUI API Health Check | PASS | 16:00:02 onap onap-uui-687788b787-sbws5 1/1 Running 0 3h 10.42.81.91 ip-10-0-0-227.us-east-2.compute.internal 16:00:02 onap onap-uui-server-78b6bf799b-2dlh7 0/1 CrashLoopBackOff 65 3h 10.42.214.7 ip-10-0-0-80.us-east-2.compute.internal
- relates to
-
USECASEUI-112 UUI fails health check on OOM deployment
- Closed
-
USECASEUI-106 UUI Health Check fails in OOM
- Closed