Thank you Ing-Wher. Yes it is exactly the issue. Mandeep has also forwarded to me the email. I should have scrolled down further to see if this had already been covered.
Lusheng Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone -------- Original message -------- From: Ing-Wher Chen <[email protected]> Date: 4/6/18 3:29 PM (GMT-05:00) To: [email protected] Cc: "JI, LUSHENG (LUSHENG)" <[email protected]> Subject: Re: problem deploying master branch oom Hi Lusheng, Might your problem be the one that Mandeep mentioned here <https://lists.onap.org/pipermail/onap-discuss/2018-April/008980.html<https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_pipermail_onap-2Ddiscuss_2018-2DApril_008980.html&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=kgnq6ZVcP9S80XVd-EMSI9FnlgZQhEYQZcvHmMzwSNo&s=_CZ27Aii97tsFW60f4eUZczLMeogcIfBS4B6yCv3AuM&e=>> and here <https://jira.onap.org/browse/OOM-858<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_OOM-2D858&d=DwMFAw&c=LFYZ-o9_HUMeMTSQicvjIg&r=qiKb3LQBLje9oy8MjG3MEx1ia4mIocif7RoUY8WQWV8&m=kgnq6ZVcP9S80XVd-EMSI9FnlgZQhEYQZcvHmMzwSNo&s=rABGn4PRQKuKEWMslBc_YH0XZvfhhOB9hcbhunluRK4&e=>>? ________________________________ > Date: Fri, 6 Apr 2018 18:28:24 +0000 > From: "JI, LUSHENG (LUSHENG)" <[email protected]> > To: Roger Maitland <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: [onap-discuss] [OOM] problem deploying master branch oom > Message-ID: <[email protected]> > 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 > README. > > 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? > > Thanks, > Lusheng Ji > ONAP DCAE
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
