-
Task
-
Resolution: Done
-
High
-
None
-
None
There was a change done to optimize the yamls - the log containers failed to create - but were not caught by the CD or the healtcheck because we are missing a call to one or all of the ELK containers
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 A rollback of the 4 changes fixes the pods ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ kubectl get pods --all-namespaces | grep log onap-log elasticsearch-1942187295-kkg1n 1/1 Running 0 10m onap-log kibana-3372627750-drmlf 1/1 Running 0 10m onap-log logstash-1708188010-1fsgl 1/1 Running 0 10m
see kibana query
- blocks
-
LOG-300
CD: OOM framework for continuous E2E deploy validation of tagged commit/merge trigger docker snapshots
-
- Closed
-
-
-
- Closed
-
-
OOM-914
Add LOG component robot healthcheck
-
- Closed
-
-
LOG-101
OOM Logging fixes tracking Epic
-
- Closed
-
- is blocked by
-
OOM-420 kibana and logstash not connecting to es
-
- Closed
-
-
-
- Closed
-
-
OOM-632
Exposing logstash port for consul to connect for health check
-
- Closed
-
-
OOM-647
State Monitoring: Log
-
- Closed
-
- relates to
-
-
- Closed
-
- mentioned in
-
Page Loading...