root@onapoom3:/home/onapuser/ONAP# docker ps --all | grep vnc
db9a2c7ec5b7
dorowu/ubuntu-desktop-lxde-vnc@sha256:7817dda9f734703eefd73a895d69411f2983e186c861048667fcd92e15
af612d "/startup.sh"
2 minutes ago Exited (143) 2 minutes ago
k8s_vnc-portal_vnc-portal-56c8b774fb-dkm4r_onap-portal_9d56a918-1075-11e8-b191-026a60b
a687a_132
439f6921a8a2 gcr.io/google_containers/pause-amd64:3.0
"/pause" 11 hours ago Up 11 hours
k8s_POD_vnc-portal-56c8b774fb-dkm4r_onap-portal_9d56a918-1075-11e8-b191-026a60ba687a_0
From: FREEMAN, BRIAN D
Sent: Tuesday, February 13, 2018 9:00 AM
To: onap-discuss@lists.onap.org
Subject: [OOM] vnc portal crashloopbackoff with newest helm/rancher
Michael,
I'm using the oom _rancher_setup_1.sh
(https://wiki.onap.org/download/attachments/8227431/oom_rancher_setup_1.sh?version=6&modificationDate=1516919271000&api=v2)
And vnc portal isnt coming up. Cant really grab any logs on it.
Most of the other components are up (had to change the public IP for dmaap in
SDC AUTO.json to be the dmaap.onap-message-router comma and comma quoated
strings.
Do I need to revert to the earlier version of helm ?
Brian
_______________________________________________
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
