Hi all, I'm having problems deploying the onap policy module due to an ImagePullBackOff error: policy-nexus-6bdf6658b-tzlxv 0/1 ImagePullBackOff Manually pull fails too: docker

It seems something related with openjdk used in the debian based image Changing the cassandra image in oom/kubernetes/aai/charts/aai-cassandra/values.yaml from cassandra:2.1 to cassandra:3.11 (that

I am trying to deploy ONAP on single VM (r4.4xlarge). There are many pod fails error 'No nodes are available that match all of the predicates: In sufficient pods'. Here is the health check output.

Hi all, During the aai deployment, the aai-cassandra chart fails with a CrashLoopBackOff error. Checking the logs, the entire error is: *** buffer overflow detected ***: java terminated =======

Hi, Stephen, AAI has completed updates to its dependencies and I have updated the wiki page: https://wiki.onap.org/x/ZzSEAQ The httpclient issue that was a problem in data-router and

Hi Victor, The script is athttps://git.onap.org/integration/tree/version-manifest/src/main/scripts/update-oom-image-versions.sh. I expect it to be run mainly by a few people from the integration

Hey Gary, Maybe that’s me, but I couldn’t find the reference to the script that you were referring. In the other hand, I’m in favor for having a “single source of truth” the only thing

Santi, As a follow-up to the Amsterdam deployment issue you were facing, it may be helpful to look into this section of the wiki which explains that multi-node k8s clusters need to have a

HI all, I've just added a script that will update the OOM helm charts using the versions from the docker-manifest.csv. This script assumes that the docker-manifest.csv contains the “definitive”

I've just added a script that will update the OOM helm charts using the versions from the docker-manifest.csv. Going forward, teams should only need to update the manifest as the "single source of

I've just added a script that will update the OOM helm charts using the versions from the docker-manifest.csv. Going forward, teams should only need to update the manifest as the "single source of

Hi Michael, The Public_IP address is my VM public IP address. I just replaced ​10.xx.xx.xx to Public_IP for security reason. ​The ARM template runs entrypoint at the end. I removed it and

I have an issue logging into the Portal in my ONAP deployment. I have described the issue here: https://jira.onap.org/browse/MUSIC-75. Basically there is a null pointer exception. How can I setup a

Mohan, Hi, pending state for your kubernetes system means that your server is not reachable from your host (same machine in this case) If you don’t wish to extend your system into a

Michael, I believe the Heat environment is using the version manifests. So I think we only have 2 places to update now - which is still one too many, but such is life. The good news is there's no

Michael, I believe the Heat environment is using the version manifests. So I think we only have 2 places to update now - which is still one too many, but such is life. The good news is there's no

Hi All, I created a Azure VM with 32vCPU and 128 GB RAM using ARM template attached in OOM-711. I ran oom_rancher_setup.sh script which is attached in OOM-715 and the script execution went well with

Gildas, Just an fyi for the TSC – there are several issues here (3) Docker sync between the 2 ONAP versions needs to be enforced – until we have the manifest completely automated with heat

Dan, Hi, I am using ONAP out of the box – no changes. The image changes anyone makes to HEAT, OOM need to also be made to the other side in order for both ONAP deployment options to be in

Dan, Hi, I am using ONAP out of the box – no changes. The image changes anyone makes to HEAT, OOM need to also be made to the other side in order for both ONAP deployment options to be in