Hi,
Same applies to dmaap in Frankfurt. Lately I did an experiment, I took config map of already deployed component (aaf): kubectl describe configmaps onap-aaf.v1 -n kube-system extracted only a Data from it (a very long one-liner) then treat it with base64 -d aaf_helm_data > aaf_helm_data_decoded.zip gzip -d aaf_helm_data_decoded.zip -c > aaf_helm_decoded It looks like helm stores also comments, function definitions a whole bunch of items. In total after decoding/unzipping aaf helm related configuration stored in k8s's config map onap-aaf.v1 contains 2604883 characters. Deployment works fine, Dmaap is operational it is just impossible to remove/update it with helm. Regards, Mateusz From: [email protected] <[email protected]> On Behalf Of Brian Freeman Sent: Thursday, July 16, 2020 5:40 PM To: [email protected]; LUCAS, JACK <[email protected]> Subject: Re: [onap-discuss] [OOM][dmaap] DMaaP Helm deployment failing This seems to be popping up again. Hadn't seen that since Beijing when we moved off the single release strategy. Did something change that the configmap is so large (or am I mis-remembering) ? Brian From: <mailto:[email protected]> [email protected] < <mailto:[email protected]> [email protected]> On Behalf Of LUCAS, JACK Sent: Thursday, July 16, 2020 11:10 AM To: <mailto:[email protected]> [email protected]; LUCAS, JACK < <mailto:[email protected]> [email protected]> Subject: Re: [onap-discuss] [OOM][dmaap] DMaaP Helm deployment failing ***Security Advisory: This Message Originated Outside of AT&T *** Reference <http://cso.att.com/EmailSecurity/IDSP.html> http://cso.att.com/EmailSecurity/IDSP.html for more information. I put the wrong log entry in my last message. The correct one is: [storage/driver] 2020/07/16 14:34:05 create: failed to create: ConfigMap "testdev123-dmaap.v1" is invalid: []: Too long: must have at most 1048576 characters [tiller] 2020/07/16 14:34:05 warning: Failed to record release testdev123-dmaap: ConfigMap "testdev123-dmaap.v1" is invalid: []: Too long: must have at most 1048576 characters (The problem occurred before, but I was not looking at DMaaP at that time and did not notice.) --- Jack Lucas From: <mailto:[email protected]> [email protected] [ <mailto:[email protected]> mailto:[email protected]] On Behalf Of LUCAS, JOHN (JACK) Sent: Thursday, July 16, 2020 11:06 AM To: <mailto:[email protected]> [email protected] Subject: [onap-discuss] [OOM][dmaap] DMaaP Helm deployment failing ***Security Advisory: This Message Originated Outside of AT&T *** Reference <http://cso.att.com/EmailSecurity/IDSP.html> http://cso.att.com/EmailSecurity/IDSP.html for more information. I'm using charts from the master branch of OOM (pulled today, 2020-07-16), and I'm using helm deploy to deploy a subset of ONAP that includes DMaaP. The helm deploy command output says that 'release "testdev123-dmaap" deployed', but helm list -all immediately after does not show testdev123-dmaap at all. (It is almost as if dmaap had not been included in the helm release at all.) The one clue I have found is in the tiller logs: [storage/driver] 2020/07/08 19:54:45 create: failed to create: ConfigMap "testdev123-dmaap.v1" is invalid: []: Too long: must have at most 1048576 characters [tiller] 2020/07/08 19:54:45 warning: Failed to record release testdev123-dmaap: ConfigMap "testdev123-dmaap.v1" is invalid: []: Too long: must have at most 1048576 characters "testdev123-dmaap.v1" is a ConfigMap that Helm creates, not something that's explicitly in the OOM charts for dmaap. Any suggestions for dealing with this issue? --- Jack Lucas -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#21721): https://lists.onap.org/g/onap-discuss/message/21721 Mute This Topic: https://lists.onap.org/mt/75543484/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
