-
Bug
-
Resolution: Not Done
-
Medium
-
None
-
None
-
None
-
R3 Sprint 1
see OOM-441
The vnc-portal pod started crashing at 2300UTC 14 Dec
The rest of the system except for the ELK onap-log elasticsearch regression is ok - portal healthcheck is OK (we should include the vnc-portal)
04:46:22 Basic Portal Health Check | PASS |
see
http://jenkins.onap.info/job/oom-cd/102/console
04:45:35 3 pending > 2 at the 27th 15 sec interval
04:45:51 onap-log elasticsearch-6df4f65775-xxszs 0/1 CrashLoopBackOff 5 8m
04:45:51 onap-portal vnc-portal-5b45665475-7tn9p 0/1 CrashLoopBackOff 6 10m
04:45:51 3 pending > 2 at the 28th 15 sec interva
l*04:45:52* report on non-running containers
04:45:52 onap-log elasticsearch-6df4f65775-xxszs 0/1 CrashLoopBackOff 5 8m
04:45:52 onap-portal vnc-portal-5b45665475-7tn9p 0/1 CrashLoopBackOff 6 10m
The last successful pod was 14th 2300UTC (The CD system was down for 4 hours after that - for migration)
Build #98 (14-Nov-2017 11:00:00 PM)
http://jenkins.onap.info/job/oom-cd/98/
23:13:23 1 pending > 0 at the 24th 15 sec interval
23:13:39 onap-aai aai-service-3869033750-jd5wn 0/1 Running 0 7m
23:13:39 1 pending > 0 at the 25th 15 sec interva
l*23:13:56* 23:13:56 1 pending > 0 at the 26th 15 sec interva
l*23:13:57*