-
Bug
-
Resolution: Done
-
Highest
-
Casablanca Release
-
POD-25, Integration SB04
-
Holmes Sprint 22
The healthcheck endpoints and ports for Holmes does not work with new images deployed
Though POD status indicate running.
root@oom-rancher:~# kubectl get pods -n onap | grep holmes
dep-holmes-engine-mgmt-547dcf697b-g4qx5 0/1 Running 300 10d
dep-holmes-rule-mgmt-5d96f677d7-mbdvh 0/1 Running 288 10d
Readiness probe fails due to endpoint/application issue.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 3m (x63002 over 10d) kubelet, oom-k8s-5 Readiness probe failed: Get http://10.42.134.137:9102/api/holmes-engine-mgmt/v1/healthcheck: dial tcp 10.42.134.137:9102: getsockopt: connection refused
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 3m (x63019 over 10d) kubelet, oom-k8s-10 Readiness probe failed: Get http://10.42.163.119:9101/api/holmes-rule-mgmt/v1/healthcheck: dial tcp 10.42.163.119:9101: getsockopt: connection refused
Blueprints templates for holmes to be reviewed and fixed if any changes required
https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-holmes-rules.yaml-template
https://git.onap.org/dcaegen2/platform/blueprints/tree/blueprints/k8s-holmes-engine.yaml-template