status checks fail and helm release does not start healthy

[testerUnito]

I am trying to install Jira DC using this helm chart using flux using. The contents of the values.yaml is attached as a screenshot above.

The Tomcat application starts but does not respond to health checks. I confirm that the localhost:8080/status returns an ERROR.

I am able to login to the instance by port-forwarding. There are some UI errors due to the fact that I'm navigating on my localhost but nothing that sheds any light.

Please help me debug this issue. If the pod fails its status checks the AWS ALB detects it as unhealthy and I'm unable to access the instance over the internet.

Pod logs:

Normal Created 16m kubelet Created container jira
Normal Started 16m kubelet Started container jira
Warning Unhealthy 15m (x11 over 16m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 503
Warning Unhealthy 15m (x2 over 15m) kubelet Readiness probe failed: Get "http://10.0.4.176:8080/status": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Warning Unhealthy 86s (x175 over 15m) kubelet Readiness probe failed: HTTP probe failed with statuscode: 500

[testerUnito]

Fixed by manually running a re-index.