Karthik, Hi, it’s Mike, welcome to ONAP. Failure of vnc-portal initialization by itself usually means you are running a currently unsupported version of helm on the server side of Kubernetes. Do a “helm version” – you should see 2.3.x on both the client and server – if you see 2.6 then you installed :latest for rancher and not v1.6.10 Verify you are running the following detailed on the wiki. Rancher 1.6.10 Kubernetes 1.8.x – to 1.8.6 Helm 2.3.x Likely you are running docker 1.12.x
Also to bring up all of ONAP you will need at least 55G. See https://jira.onap.org/browse/OOM-441 https://jira.onap.org/browse/OOM-486 Thank you /michael From: [email protected] [mailto:[email protected]] On Behalf Of Karthik Sent: Tuesday, January 9, 2018 10:19 To: [email protected] Subject: [onap-discuss] OOM Installation Problem | Unable to bring up Portal Pod Hi Team , Good day ! I followed the Quick Installation<https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation> steps to install ONAP. All pods are up and running except "Portal".I tried multiple times to bring up "Portal" pod , but could not able to solve the problem . "portalapps", "vnc-portal" are keep on hangs with Waiting:PodInitializing status. I have attached the log and status images . Please refer it and reply to me if you could help me in this problem. Environment Details: Ubuntu 16, RAM 50 GB. Thanks in Advance. Regards, Karthik. This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
