-
Bug
-
Resolution: Done
-
High
-
El Alto Release, Frankfurt Release
The pod aai-datarouter seems to always fail.
it can be seen on mostof the last gating https://orange-opensource.gitlab.io/lfn/onap/xtesting-onap-view/index.html and on the Orange Daily https://gitlab.com/Orange-OpenSource/lfn/onap/xtesting-onap/-/jobs/365830160
logs are available 98967-1
e.g. for gating https://orange-opensource.gitlab.io/lfn/onap/xtesting-onap-view/results/98967-1/k8s/onap-k8s.log
Normal Pulled 36m (x11 over 71m) kubelet, worker07-onap-gating-1 Successfully pulled image "nexus3.onap.org:10001/onap/data-router:1.5.1"
Warning Unhealthy 6m40s (x35 over 71m) kubelet, worker07-onap-gating-1 Readiness probe failed: dial tcp 10.233.73.220:9502: connect: connection refused
Warning BackOff 107s (x269 over 71m) kubelet, worker07-onap-gating-1 Back-off restarting failed container
and in the log
2019/11/29 16:12:18.663281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls.onap on 10.233.0.3:53: no such host
....
2019/11/29 17:12:13.856938 log.go:116: INFO File is inactive: /var/log/onap/datarouter-prov/jetty.log. Closing because close_inactive of 5m0s reached.
2019/11/29 17:12:13.856948 log.go:116: INFO File is inactive: /var/log/onap/datarouter-prov/apicalls.log. Closing because close_inactive of 5m0s reached.
2019/11/29 17:12:13.870931 log.go:116: INFO File is inactive: /var/log/onap/datarouter-prov/errors.log. Closing because close_inactive of 5m0s reached.
...
2019/11/29 17:12:30.029843 sync.go:85: ERR Failed to publish events caused by: write tcp 10.233.72.153:42576->10.233.63.40:5044: write: connection reset by peer
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-