-
Bug
-
Resolution: Done
-
Highest
-
Amsterdam Release
-
None
kibana and logstash not connecting to es when using namespace different from onap
20171115: Michael O'Brien
------------------------------------
The templating "tpl" function should work - see https://github.com/kubernetes/helm/issues/2492
Noticed that log containers were no longer showing up today - as I have a new CD job - but it does not have a log heathcheck up - verified the issue below
The OOM CD job picked this up at 18:07 UTC 20171114 http://jenkins.onap.info/job/oom-cd/93/console
18:07:15 ********** Creating deployments for log ********** 18:07:15 18:07:15 Creating namespace ********** 18:07:15 namespace "onap-log" created 18:07:15 18:07:15 Creating service account ********** 18:07:15 clusterrolebinding "onap-log-admin-binding" created 18:07:15 18:07:15 Creating registry secret ********** 18:07:15 secret "onap-docker-registry-key" created 18:07:15 18:07:15 Creating deployments and services ********** 18:07:15 Error: parse error in "log/templates/logstash-deployment.yaml": template: log/templates/logstash-deployment.yaml:83: function "tpl" not defined 18:07:15 The command helm returned with error code 1 18:07:15 wait for all pods up for 10 min
see kibana query
- blocks
-
INT-106 Stabilizing the ONAP master branch
- Closed
-
LOG-333 OOM vnc-portal container down since 20171114:2300UTC after helm upgrade from 2.3 to 2.6 and Rancher 1.6.11 on same day
- Closed
-
OOM-427 log containers fail to create since 20171213 - using tpl template function on helm 2.3 not 2.6
- Closed
-
OOM-428 Add log container healthcheck to mark failed creations - see OOM-427
- Closed
-
LOG-101 OOM Logging fixes tracking Epic
- Closed
- is blocked by
-
OOM-429 DOC: Document HELM server version 2.7.2 required for tpl usage
- Closed
- relates to
-
LOG-335 Any Helm error in createAll breaks all pods in queue after the error - refactor for individual parallel pods
- Closed
- links to