Re: [onap-discuss] [oom] [rancher/k8s deployment] (amsterdam release) error on onap-consul app

Hi Mohan, I guess this might be something to do with your Rancher setup. Try the following. 1) Check all your kube-system containers are up and running properly 2) Make sure that OOM host IP is mapped in the /etc/hosts file # OOM_HOST_IP{HOST_NAME} 3) Make sure that your kube-dns

Re: [onap-discuss] Amsterdam Portal issue

Hi Seaudi, Could you give me more information, all ONAP container persistent data files are stored under /dockerdata-nfs/onap folder. We should get all the data back when you reboot the server. I am not quite sure what you did, i hope the ONAP VM/server IP did not change when you restarted the

Re: [onap-discuss] [oom] [rancher/k8s deployment] (amsterdam release) error on onap-consul app

*helm-v2.3.0-linux-amd64.tar.gz* tar -zxvf helm-v2.3.0-linux-amd64.tar.gz sudo mv linux-amd64/helm /usr/local/bin/helm # Clone the amsterdam relase repository git clone -b amsterdam http://gerrit.onap.org/r/oom You can give it a try. Regards Vivek On Mon, May 21, 2018 at 10:28 PM, Viveka

[onap-discuss] Beijing Kubernetes service level dependencies

Hi All, We see that there are close to 142 Kubernetes containers getting started as part of Beijing deployment. We would like understand how ONAP services are dependent on each other. Do we have any Wiki page discussing about ONAP service level dependencies? Regards Vivek

[onap-discuss] Beijing Kubernetes OOM portal is not coming up

Hi All, We are not able to access oom portal after deploying Beijing release. We did see the portal coming up 2 days back, now it seems to be broken. Here is the list of logs for your reference, it seems like 4 PODs failing to start with Image pull error and it continues to stay there for more

[onap-discuss] OOM k8s Beijing/2.0.0-ONAP Helm build fails for nodeSelector attribute in values.yaml

Hi All, We need some help regarding *nodeSelector* attribute definition in ONAP OOM kubernetes values.yaml file. When we included the nodeSelector attribute, the Helm package make failed. *Here is what we did.* 1) Created 2 node Rancher + Kubernetes cluster 2) Created the following labels

Re: [onap-discuss] OOM k8s Beijing/2.0.0-ONAP Helm build fails for nodeSelector attribute in values.yaml

> > > It should have the same indentation as volumes. > > > > > > *-- K i r a n* > > > > *From:* onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] *On > Behalf Of *Vivekanandan Muthukrishnan > *Sent:* Thursday, August 02, 2018 11:22 AM &g

Re: [onap-discuss] OOM k8s Beijing/2.0.0-ONAP Helm build fails for nodeSelector attribute in values.yaml

/oom/kubernetes/aai/charts/aai-champ/templates/deployment.yaml On Fri, Aug 3, 2018 at 6:30 AM, Vivekanandan Muthukrishnan < vmuthukrish...@aarnanetworks.com> wrote: > Hi Kiran, > > Thanks for the quick response. We will try this workaround and update you > soon. > > Regards

Re: [onap-discuss] ONAP Portal is not loading A and xDemoApp UI

Hi Steve, Thanks for the quick response and this is really helpful. Could you help us with the following clarifications. 1) A Application on boarding Password value? Username = aaiui Password = (What is the values for this one) 2) We are kind of confused

Re: [onap-discuss] ONAP Portal is not loading A and xDemoApp UI

Hi Steve, Thanks for pointing to the YAML file. It seems like we will have to apply the patch OOM-1117 & OOM-347 and then upgrade the AAI service. We will send our updates by early next week. Regards Vivek On Fri, Aug 10, 2018 at 11:24 PM, Steve Siani <

Re: [onap-discuss] ONAP Portal is not loading A and xDemoApp UI

Hi Manoop, We will look into the OOM-1117 & OOM-347 and apply the changes in AAI and xDemo APP component. Thanks for sending us the earlier discussions in this regard. Regards Vivek On Fri, Aug 10, 2018 at 11:24 PM, Steve Siani < alphonse.steve.siani.djissit...@ibm.com> wrote: > Hi Vevek, >

Re: [onap-discuss] OOM k8s Beijing/2.0.0-ONAP Helm build fails for nodeSelector attribute in values.yaml

; > Maybe try something with sed? That might help in doing the replacement > across all the files. > > > > If you can wait, I can upload a patch that fixes the indentation today. > > > > *-- K i r a n* > > > > *From:* onap-discuss@lists.onap.org [mailto:onap-di

Re: [onap-discuss] ONAP Beijing k8s vFW VID service deployment failed with SVC3001 error

Hi All, Here is the VID screen shot for your reference. Thanks & Regards Vivek On Thu, Jul 19, 2018 at 9:54 PM, Vivekanandan Muthukrishnan < vmuthukrish...@aarnanetworks.com> wrote: > Hi All, > > We deployed ONAP Beijing k8s and able on board vFW service and distributed

[onap-discuss] ONAP Beijing k8s vFW VID service deployment failed with SVC3001 error

Hi All, We deployed ONAP Beijing k8s and able on board vFW service and distributed the same from SDC. However the Service instance creation (Deploy) failed at the VID UI. It seems like something went wrong at the AAI side, it looks like AAI is not persisting the SDC service models. We looked at

Re: [onap-discuss] OOM errors cannot deploy ONAP - with error logs

Hi Abdel, It seems like you are having some internet connective issues and many of your containers are in "ImagePullBackOff" state. Kindly check your net connection and redeploy the oom containers again. Regards Vivek On Sat, Mar 3, 2018 at 10:28 PM, wrote:

Re: [onap-discuss] oom Failed to pull image "nexus3.onap.org:10001/onap/refrepo:1.0-STAGING-latest"

Console Error Message* Error code: SVC4614 Status code: 400 Invalid content. Group type org.openecomp.groups.heat.HeatStack does not exist *SDC Console Image* On Sat, Mar 3, 2018 at 5:59 PM, Vivekanandan Muthukrishnan < vmuthukrish...@aarnanetworks.com>

Re: [onap-discuss] Amsterdam Kubernetes OOM SDC UI is not accessible

nd running (2/2) > > > > Hope this helps. > > > > Thanks, > > Borislav Glozman > > O:+972.9.776.1988 > > M:+972.52.2835726 > > [image: amdocs-a] > > *Amdocs a **Platinum member of ONAP* > <https://www.amdocs.com/open-network/nfv-powere

Re: [onap-discuss] oom Failed to pull image "nexus3.onap.org:10001/onap/refrepo:1.0-STAGING-latest"

Hi All, Has any faced this issue. Please let us know if there is any workaround for the below issue. Regards Vivek On Sun, Mar 4, 2018 at 7:06 PM, Vivekanandan Muthukrishnan < vmuthukrish...@aarnanetworks.com> wrote: > Hi All, > > It looks like we are not able to create the

Re: [onap-discuss] Amsterdam Kubernetes OOM SDC UI is not accessible

fine. > See https://jira.onap.org/browse/OOM-766 > > Alexis > > On Mar 5, 2018, at 6:03 AM, Vivekanandan Muthukrishnan < > vmuthukrish...@aarnanetworks.com> wrote: > > Hi Borislav, > > Thanks for the support. > > Yes, we did the same and we are able to create a

[onap-discuss] Amsterdam SDNC user creation fails with : Unable to get database connection. Error: connect ECONNREFUSED 127.0.0.1:3306

Hi All, We are not able to create SDNC portal user, and it seems like some issue initialising the the SDNC container. Here is the logs for your reference. Can someone help us to workaround this issue would be really great. Regards Vivek *SDC Container status* onap-sdnc

[onap-discuss] oom Failed to pull image "nexus3.onap.org:10001/onap/refrepo:1.0-STAGING-latest"

Hi All, Do we know the reason for the below failure, it seems like all the OOM pod's have comeup successfully except the below one. NAMESPACE NAME READY STATUS RESTARTS AGE onap-vnfsdk refrepo-1924147637-6qn48

[onap-discuss] Amsterdam Kubernetes OOM SDC UI is not accessible

Hi All, We are setting up Amsterdam kuberneter oom. The deployment went fine, even the ONAP portal login works fine. However when we try to access the SDC portal it is keep throwing 503 error message. And we looked at the SDC-BE and SDC-ES logs and it seems like the elastic serach container

[onap-discuss] Beijing ONAP k8s 2.0.0 portal VID Error HTTP Status 500 - Servlet.init()

All, We successfully deployed ONAP Beijing k8s 2.0.0 and it was running fine for more than a month. We rebooted the server after applying some patches. After that ONAP Portal is not able to load VID UI and started throwing HTTP 500 Error. We looked at the VID logs, it seems like