-
Bug
-
Resolution: Won't Do
-
High
-
Beijing Release
-
None
-
None
on latest beijing deployments, I am unable to spawn helm
(f6f13f455b1f98011df9700609a4fbc11e4ba260)
{ "changed": true, "cmd": [ "helm", "install", "local/onap", "-n", "dev", "--namespace", "onap" ], "delta": "0:00:58.371159", "end": "2018-11-08 15:43:48.898636", "msg": "non-zero return code", "rc": 1, "start": "2018-11-08 15:42:50.527477", "stderr": "Error: getting deployed release \"dev\": release: \"dev\" not found", "stderr_lines": [ "Error: getting deployed release \"dev\": release: \"dev\" not found" ], "stdout": "NAME: dev", "stdout_lines": [ "NAME: dev" ] }
[storage/driver] 2018/11/08 20:43:47 create: failed to create: ConfigMap "dev.v1" is invalid: data: Too long: must have at most 1048576 characters
[tiller] 2018/11/08 20:43:47 warning: Failed to record release dev: ConfigMap "dev.v1" is invalid: data: Too long: must have at most 1048576 characters
It looks that latest commits in beijing branch added some new stuff into aai configMap and overal size exceeeded that limit.
For a fix we might do it similarly like in (master branch)
https://jira.onap.org/browse/OOM-1061
https://gerrit.onap.org/r/#/c/46673/
maybe I can backport this bugfix in Beijing as proposal ....