-
Bug
-
Resolution: Done
-
Highest
-
Beijing Release
20180224 update: https://gerrit.onap.org/r/#/c/28291/6
fix: https://gerrit.onap.org/r/#/c/24225/1 and Rancher 1.6.10 (not 1.6.11 with helm 2.6.1 instead of helm 2.3.0)
docker run -d --restart=unless-stopped -p 8880:8080 rancher/server:stable
Issue:
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)
Went through the commits the only one that went in at that time is https://gerrit.onap.org/r/#/c/23247/ under -------- that forced a helm 2.6 upgrade as part of Rancher 1.6.11OOM-420
Gerrit Code Review Nov 14 12:32 PM Change has been successfully merged by Yury Novitsky
But nothing should affect vnc-portal - it is self contained
Turns out that the helm 2.3 upgrade to 2.6 is breaking this.
Server version in Rancher 1.6.11 is 2.6, but in 1.6.10 it is 2.3
https://hub.docker.com/r/rancher/server/tags/
v1.6.11 351 MB 3 days ago
Check versions
AWS current ubuntu@ip-172-31-23-250:~$ docker images | grep vnc dorowu/ubuntu-desktop-lxde-vnc latest 65906f49c700 2 weeks ago 1.311 GB nexus3.onap.org:10001/dorowu/ubuntu-desktop-lxde-vnc latest 65906f49c700 2 weeks ago 1.311 GB 2 week old internal oom/kubernetes/oneclick# docker images | grep vnc dorowu/ubuntu-desktop-lxde-vnc latest 65906f49c700 2 weeks ago 1.311 GB nexus3.onap.org:10001/dorowu/ubuntu-desktop-lxde-vnc latest 65906f49c700 2 weeks ago 1.311 GB dorowu/ubuntu-desktop-lxde-vnc <none> 5f7af1a8a2a4 3 months ago 1.251 GB nexus3.onap.org:10001/dorowu/ubuntu-desktop-lxde-vnc <none> 5f7af1a8a2a4 3 months ago 1.251 GB
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*
Tried running older version of vnc-portal from before 24 days ago
https://hub.docker.com/r/dorowu/ubuntu-desktop-lxde-vnc/tags/
- blocks
-
INT-106 Stabilizing the ONAP master branch
- Closed
-
OOM-535 Upgrade Kubernetes from 1.8.6 to 1.9.2
- Closed
-
OOM-413 In portal VNC pod refresh /etc/hosts entries
- Closed
-
OOM-486 HELM upgrade from 2.3 to 2.8.0
- Closed
-
OOM-429 DOC: Document HELM server version 2.7.2 required for tpl usage
- Closed
-
OOM-442 Add vnc-portal to the OOM portal healthcheck - it passes when vnc-portal is down
- Closed
-
OOM-820 Bypass vnc-portal for ONAP portal access
- Closed
- is blocked by
-
OOM-420 kibana and logstash not connecting to es
- Closed
-
LOG-314 Rancher 1.6.13 will run docker 17.03.2 via K8S 1.8 (up from 1.12 for K8S 1.7)
- Closed
-
OOM-552 Segregation of configuration for APPC component
- Closed
- relates to
-
LOG-336 Refactor for v1.6.10 due to new rancher docker image 1.6.12 listed as stable
- Closed
-
OOM-427 log containers fail to create since 20171213 - using tpl template function on helm 2.3 not 2.6
- Closed
-
LOG-335 Any Helm error in createAll breaks all pods in queue after the error - refactor for individual parallel pods
- Closed
-
LOG-287 Rancher 2.1 deployment POC
- Closed
-
OOM-444 MSO and SDC healthcheck fail under new Rancher 1.6.11(helm 2.6.1)
- Closed
-
PORTAL-212 Portal URL and VNC Container
- Closed
- links to
- mentioned in
-
Page Loading...