Might your problem be the one that Mandeep mentioned here
<https://lists.onap.org/pipermail/onap-discuss/2018-April/008980.html> and here
> Date: Fri, 6 Apr 2018 18:28:24 +0000
> From: "JI, LUSHENG (LUSHENG)" <l...@research.att.com>
> To: Roger Maitland <roger.maitl...@amdocs.com>
> Cc: "firstname.lastname@example.org" <email@example.com>
> Subject: [onap-discuss] [OOM] problem deploying master branch oom
> Message-ID: <ad78eff2-b467-4dd8-9eb2-6a0adb379...@research.att.com>
> Content-Type: text/plain; charset="utf-8"
> Hi Roger,
> I am having trouble deploying the current OOM master branch this morning. I
> am using a K8s cluster created on a Windriver lab
> xxlarge VM. Then cloned oom and going through the Helm steps as listed in
> All the steps went fine until the last ?helm install? step. The Helm release
> installation failed and no Helm release was created.
> Pods were queued to be created but I am not sure whether they would be in
> good shape even if they eventually do come up for
> the reason below.
> I looked into the problem and it appears that the Tiller was not able to
> create config map:
> [storage/driver] 2018/04/06 18:00:17 create: failed to create: ConfigMap
> "dev.v1" is invalid: data: Too long: must have at most
> 1048576 characters
> [tiller] 2018/04/06 18:00:17 warning: Failed to record release dev: ConfigMap
> "dev.v1" is invalid: data: Too long: must have at
> most 1048576 characters
> Any advice on how we could proceed?
> Lusheng Ji
> ONAP DCAE
onap-discuss mailing list