Pavithra, Master has been patched (Thanks Alexis )with https://gerrit.onap.org/r/#/c/24225
http://jenkins.onap.info/job/oom-cd/407/ was pre patch – stopped the build http://jenkins.onap.info/job/oom-cd/408 will run without the patch – a clean master – check this before pulling if you require – will be finished by 1200EDT. Thank you /michael From: Michael O'Brien Sent: Monday, November 27, 2017 11:13 To: 'Alexis de Talhouët' <[email protected]>; 'Sauvageau, David' <[email protected]> Cc: [email protected] Subject: RE: [onap-discuss] Issue in ONAP Amsterdam release installation Hi, yes, good point, there is a pending merge for master that should be merged by this Wed that is already fixed in the 1.1.0 branch – I am assuming you are using master. The current workaround is to add the revert patch below. I am going to push a bit harder right now to get the master fix merged so you can continue without having to patch. https://gerrit.onap.org/r/#/c/24225 git pull https://gerrit.onap.org/r/oom refs/changes/25/24225/1<https://gerrit.onap.org/r/oom%20refs/changes/25/24225/1> The issue is that under our recommended Helm 2.3.0 version – any Helm 2.6+ functions will not work. In the future we will be upgrading to Helm 2.7 (the new Rancher 1.6.11 out last week used Helm 2.6) – but for now use the rancher stable release and add the patch below. https://jira.onap.org/browse/OOM-420 https://jira.onap.org/browse/OOM-427 https://jira.onap.org/browse/OOM-441 Guys we need the master patch https://gerrit.onap.org/r/#/c/24225/ merged in master - as we can revisit the helm upgrade outside of master - we need to accomidate the community without them having to patch master in https://lists.onap.org/pipermail/onap-discuss/2017-November/006546.html Alex, David can we get this patch pushed to master today as there are 5-7 teams experiencing this right now and the fix has been verified several times since the 16th It is also in the CD job since the weekend when we switched back to AWS – where I have a patch.sh running on top of master until then. http://jenkins.onap.info/job/oom-cd/406/console 15:09:26 NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE 15:09:26 elasticsearch 10.43.215.254 <nodes> 9200:30254/TCP 1s 15:09:26 elasticsearchtcp 10.43.32.12 <none> 9300/TCP 1s 15:09:26 logstash 10.43.7.213 <none> 5044/TCP 1s 15:09:26 kibana 10.43.49.127 <nodes> 5601:30253/TCP 1s /michael From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alexis de Talhouët Sent: Monday, November 27, 2017 10:44 To: Pavithra R13 <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] Issue in ONAP Amsterdam release installation Hi, This is due to an error that slept in the release, but was reverted. Please pull latest code from the release-1.1.0 branch, and you should be all good. Explanation wrt this issue is, the helm version for “tpl” function is 2.3+. You must have an inferior version, which is ok for Amsterdam release. For more information, please read comments here: https://gerrit.onap.org/r/#/c/24225/ Thanks, Alexis On Nov 23, 2017, at 7:00 AM, Pavithra R13 <[email protected]<mailto:[email protected]>> wrote: Hi, We are trying to setup ONAP Amsterdam release and we are facing the below error during log component installation(./createAll.bash -n onap -a log). Error: parse error in "log/templates/kibana-deployment.yaml": template: log/templates/kibana-deployment.yaml:71: function "tpl" not defined The command helm returned with error code 1 Kindly help us in resolving the issue. Thanks & Regards, Pavithra R _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
