-
Bug
-
Resolution: Done
-
Highest
-
Amsterdam Release
-
None
Rolled back the change merged yesterday (kibana/logstash-deployment.yaml) - and tested it
Looks like the original change to work around the hardcoded onap namespace was not tested properly.
The templating "tpl" function should work - see https://github.com/kubernetes/helm/issues/2492
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
ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ kubectl get pods --all-namespaces | grep log ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ ./createAll.bash -n onap -a log ********** Creating instance 1 of ONAP with port range 30200 and 30399 ********** Creating ONAP: ********** Creating deployments for log ********** Creating namespace ********** namespace "onap-log" created Creating service account ********** clusterrolebinding "onap-log-admin-binding" created Creating registry secret ********** secret "onap-docker-registry-key" created Creating deployments and services ********** Error: parse error in "log/templates/kibana-deployment.yaml": template: log/templates/kibana-deployment.yaml:72: function "tpl" not defined The command helm returned with error code 1 ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ vi ../log/templates/logstash-deployment.yaml ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ vi ../log/templates/kibana-deployment.yaml ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ ./deleteAll.bash -n onap -a log ********** Cleaning up ONAP: Error: release: not found namespace "onap-log" deleted clusterrolebinding "onap-log-admin-binding" deleted Service account onap-log-admin-binding deleted. Waiting for namespaces termination... ********** Gone ********** ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ ./createAll.bash -n onap -a log ********** Creating instance 1 of ONAP with port range 30200 and 30399 ********** Creating ONAP: ********** Creating deployments for log ********** Creating namespace ********** namespace "onap-log" created Creating service account ********** clusterrolebinding "onap-log-admin-binding" created Creating registry secret ********** secret "onap-docker-registry-key" created Creating deployments and services ********** NAME: onap-log LAST DEPLOYED: Wed Nov 15 03:23:39 2017 NAMESPACE: onap STATUS: DEPLOYED RESOURCES: ==> v1/Service NAME CLUSTER-IP EXTERNAL-IP PORT(S) AGE elasticsearch 10.43.244.48 <nodes> 9200:30254/TCP 1s elasticsearchtcp 10.43.36.48 <none> 9300/TCP 1s logstash 10.43.33.104 <none> 5044/TCP 1s kibana 10.43.176.68 <nodes> 5601:30253/TCP 1s ==> extensions/v1beta1/Deployment NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE kibana 1 1 1 0 1s logstash 1 1 1 0 1s elasticsearch 1 1 1 0 1s ==> v1/ConfigMap NAME DATA AGE kibana-configmap 1 1s logstash-configmap 2 1s elasticsearch-configmap 1 1s ==> v1/PersistentVolume NAME CAPACITY ACCESSMODES RECLAIMPOLICY STATUS CLAIM REASON AGE elasticsearch-db 2Gi RWX Retain Bound onap-log/elasticsearch-db 1s ==> v1/PersistentVolumeClaim NAME STATUS VOLUME CAPACITY ACCESSMODES AGE elasticsearch-db Bound elasticsearch-db 2Gi RWX 1s **** Done **** ubuntu@ip-172-31-25-96:~/oom/kubernetes/oneclick$ kubectl get pods --all-namespaces | grep log onap-log elasticsearch-1942187295-9wxrd 0/1 Running 0 14s onap-log kibana-3372627750-ncqmg 0/1 Init:0/1 0 14s onap-log logstash-1708188010-z58np 0/1 Init:0/1 0 14s 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
- blocks
-
OOM-428 Add log container healthcheck to mark failed creations - see OOM-427
-
- Closed
-
-
LOG-99 Fix data loss due to no matching elasticsearch template
-
- Closed
-
-
LOG-101 OOM Logging fixes tracking Epic
-
- Closed
-
- is blocked by
-
OOM-420 kibana and logstash not connecting to es
-
- Closed
-
- relates to
-
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
-
-
LOG-335 Any Helm error in createAll breaks all pods in queue after the error - refactor for individual parallel pods
-
- Closed
-
-
LOG-287 Rancher 2.1 deployment POC
-
- Closed
-
-
PORTAL-212 Portal URL and VNC Container
-
- Closed
-
- mentioned in
-
Page Loading...