Viswa, Sorry for the late reply – a fellow ONAP teammate alerted me to your message we missed – however we would not have had an answer on these NFS failures until 12 days later anyway.
I would expect you did not run the init-config container first – this is ok I had this issue as well until the 16th (The failure pods – match exactly the ones I previously saw before 16 July) – I only figured out I was missing that step then and added it to the wiki on 16 July. root@obriensystemsucont0:~/onap/oom/kubernetes/config# kubectl create -f pod-config-init.yaml https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-QuickstartInstallation https://jira.onap.org/browse/OOM-1 Try bringing up the config-init container first – then all your other pods will be able to see the mount you created on your system at /dockerdata-nfs/onapdemo This will fix 33 of 34 containers (there are still 11 more container pending for DCAE in the queue). Only the drools container under onap-policy is still having timeout issues pulling artifacts. Thank you /michael From: [email protected] [mailto:[email protected]] On Behalf Of Viswa KSP Sent: Tuesday, July 4, 2017 11:12 To: [email protected] Subject: [onap-discuss] [OOM] Using OOM kubernetes based seed code over Rancher Dear OOM Team, I tried to bring up OOM seed code ( https://gerrit.onap.org/r/gitweb?p=oom.git ) using Rancher as per wiki ( https://wiki.onap.org/display/DW/ONAP+on+Kubernetes ). However certain PODs on several ONAP namespaces, didn't come up well. All failed PODs show similar error pattern. Following are the status of all PODs currently. Namespace POD Status onap-aai aai-service Up hbase Up model-loader-service Down onap-appc appc Up appc-dbhost Up appc-dgbuilder Up onap-message-router dmaap Up global-kafka Up zookeeper Up onap-mso mso Up mariadb Up onap-policy brmsgw Down drools Down mariadb Up nexus Up Pap Up Pdp Down Pypdp Down onap-portal portalapps Down portaldb Up vnc-portal Down onap-robot robot Up onap-sdc sdc-be Down sdc-cs Up sdc-es Up sdc-fe Down sdc-kb Down onap-sdnc sdnc Up sdnc-dbhost Up sdnc-dgbuilder Up sdnc-portal Up onap-vid vid-mariadb Up vid-server Down PODs which are in failed state show below errors : Error syncing pod, skipping: failed to "InitContainer" for "vid-server-readiness" with RunInitContainerError: "init container \"vid-server-readiness\" exited with 1" Any help would be highly appreciated. PS : I had earlier asked subset of this question as a follow-up question in another thread. Then realized this discussion would help future developers. So starting this new thread with appropriate email subject for easy search & retrieval. BR, Viswa 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
