The problem is with the last round of changes to project helm charts the configMap has exceeded the boundary.
There is a change being tested to use a new approach for installation from the OOM team to use a per project release that solves the problem. Its a new deploy/undeploy plugin to helm. Mike Elliot has details but we havent finished testing yet. I thought I had heard that removing the comments at the top of the helm charts for license info might also provide some temporary relief since comments if not wrapped correctly are kept in the configMap but that might be tedious. Mike can add more on the new deploy approach. Brian From: [email protected] <[email protected]> On Behalf Of Krzysztof Kuzmicki Sent: Wednesday, September 19, 2018 5:20 AM To: [email protected] Subject: [onap-discuss] Onap installation issue "Error: getting deployed release "dev": release: "dev" not found" Hi We are facing strange issue during fresh installation of Casablance release. After "make all" and "helm install local/onap -n dev --namespace onap" we got following error: NAME: dev Error: getting deployed release "dev": release: "dev" not found After this error installation starts in kuberentes however upgrades are not possible due to lack of release dev.. We tried also reduce amount of ONAP components (15 set to false)in kubernetes/onap/values.yaml issue still exists. Has anybody noticed same issue? Is for that some jira issue reported? Maybe is for that some workaround? br, Krzysztof -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12515): https://lists.onap.org/g/onap-discuss/message/12515 Mute This Topic: https://lists.onap.org/mt/25753829/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
