Dear All, We have deployed the Onap master branch of Frankfurt and meet the same issue which is opened in https://jira.onap.org/browse/OOM-2534 SDC and SDNC modules could not be installed successfully

#oom #helm

I ran into the issue as well. Very similar to yours. It was related to OOM-2534 per OOM team. They are still working on it. Thanks, Xin Miao Solution Engineering Fujitsu Network Communication (W)972-4

#oom #helm

Ok. Thanks guys. Should have checked Jira first. :)

#oom #helm

There are a couple of charts affected. See https://jira.onap.org/browse/OOM-2566 Von: onap-discuss@... <onap-discuss@...> Im Auftrag von Fiachra Corcoran Gesendet: Freitag, 2. Ok

#oom #helm

I have observed this as well. I believe the problem is that for each release, Helm creates a configMap to keep data that Helm needs to manage the release. For some of the component releases, the data

#oom #helm

Hi OOM Team, When deploying master branch, I am seeing odd behaviour from helm. The "deploy" cmd shows the relevant components get deplopyed: helm deploy onap local/onap --namespace onap -f ~/onap-ove

#oom #helm

Dear Taka, Thank you for your advice. Previously I git pull by 'git clone -b 5.0.1-ONAP http://gerrit.onap.org/r/oom --recurse-submodules'. I pull the head of master this time. And it works, thank you

#appc #helm

I saw your failure was on common/etcd. Did you git pull to the head of master for the all OOM repo? Taka APPC PTL

#appc #helm

Hi, I want to deploy APP-C for testing its capability, and I follow oom_quickstart_guide And I use Helm 2.16.1, macOS Catalina version 10.15.1 However, after I modified 'appc enable: true' and run 'ma

#appc #helm

Hi All, I am trying to deploy aaf and dmaap in a 3 node Cluster (1 Control plane and 2 Worker VM's). dmaap is failing and you can see 2 JOBS are not coming up successfully. Cant figure out what i am m

#aaf #dmaap #dublin #helm

Hi, I found the issue. I used 1 worker node and aaf didnt come up fine. When i tried deploying aaf and dmaap in 1 controlplane + 2 worker nodes then everything came up fine. Thanks for your help. Ragh

#dmaap #helm

Hi Raghu, Please share the full log of the message router. If the log you shared is the full log of the message router , increase the initial delay for the liveliness check. Thanks, Sunil

#dmaap #helm

Brian, I tried helm deploy and getting same issue aarna@dublin-test-01:~/oom/kubernetes$ helm deploy dev local/aaf --namespace onap --timeout 900 fetching local/aaf release "dev" deployed aarna@dublin

#dmaap #helm

I think you want to use helm deploy not hedlm install Sent via the Samsung Galaxy S8, an AT&T 5G Evolution capable smartphone

#dmaap #helm

Brian, I tried to install only aaf and dmaap in my setup. I installed aaf using the following command (Didnt change any sleep values in the yaml file) helm install --debug local/aaf -n dev-aaf --names

#dmaap #helm

Brian, Thanks a lot for your input. Let me try again with the steps mentioned by you. Thanks Raghu

#dmaap #helm

Thats not the sequence we usually use for a project re-deployment DMAAP project does alot of post instantiate configuration s you may hae to adjust your timeout 900 to a longer interval – usually helm

#dmaap #helm

Hi , I deployed ONAP by following the guide https://onap.readthedocs.io/en/dublin/submodules/oom.git/docs/oom_quickstart_guide.html#quick-start-label I deployed all ONAP components using onap-all.yml

#dmaap #helm

Hi, removing old configmaps versions and limiting the helm history to 5-10 versions did the trick for me. > https://github.com/helm/helm/issues/2332#issuecomment-336565784 Regards David -- David Pérez

#oom #helm #casablanca #lfn #kubernetes

Hi, I am starting to get errors like the one below when deploying/undeploying with helm, branch Casablanca, running for ~70 days. # helm undeploy dev-sniro-emulator --purge Error: trying to send messa

#oom #helm #casablanca #lfn #kubernetes