Hi Pulkit,
The OOM team noticed this and created a defect to track the fix which is 
currently a top priority and has a gerrit review outstanding.  I believe it 
will be wrapped up and merged today.

The root cause is this: portal has a sql file that is extremely large because 
it contains images (binary data).
This is exhausting the config map space so we have removed it and found an 
alternate way of injecting it in the portals db instantiation.  The fix can 
also be used to reduce other config maps that really do not need to be part of 
the helm package.  This was important to us to ensure that it is not just a 
band-aid fix specific to one app.


Begin forwarded message:

From: Pulkit Walia <pwa...@vmware.com<mailto:pwa...@vmware.com>>
Subject: [onap-tsc] ONAP-OOM Deployment Error
Date: April 6, 2018 at 6:35:06 AM EDT
To: "onap-disc...@lists.onap.org<mailto:onap-disc...@lists.onap.org>" 

Hi All,

I need some help related to ONAP Deployment.
I am trying to deploy ONAP on VMware Integrated OpenStack 4.0 with Kubernetes 
and I have been facing an error with it.

I am using the following for ONAP deployment:

  *   VMware Integrated OpenStack 4.0 with Kubernetes
  *   Helm v2.7.0
  *   Kubectl v1.7.0
  *   ONAP-OOM Repository http://gerrit.onap.org/r/oom

I enabled all the components as true in the oom/kubernetes/onap/values.yaml 
file except the portal component, it was disabled.
During this configuration, the deployment was successful using Helm.

But the problem arises when I enable portal component as true in the yaml file. 
The deployment is unsuccessful and I get the following error:


In the above screenshot, after a successful deployment I am upgrading the 
deployment after enabling the portal component in the yaml file. After that, 
“data: Too Long: …” error is triggered always, in all the versions of Helm.
I think the portal components is flooding the Kubernetes ConfigMap with large 
amount of data that it is unable to handle.

The kubectl and helm version screenshot is as follows:


I have a few doubts/questions regarding this, they are as follows:

  *   Is this a known issue in ONAP Deployment?
  *   Is the portal component responsible for this error?
  *   Is this an issue related to Helm v2.7.x?
  *   Is this an issue related to Kubectl Version?
  *   Is this caused due to VMware Integrated OpenStack with Kubernetes 4.0?
  *   Is this caused due to lack of RAM in the Master and Worker Node Instances 
? (Right now, each of the instance has 32 vCPUs, 128 GB RAM, 256 GB Size)
  *   If not due to one of the reasons above, then what is the cause of this 

It will be really helpful if someone from the ONAP Community can put some of 
their suggestions on this, or someone who has faced the same issue and knows 
the solutions to this error.

Thank You and Regards,
Pulkit Walia

ONAP-TSC mailing list

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 
ONAP-TSC mailing list

Reply via email to