Sonarqube Stopped Working with Recent Image Updates

We have been deploying Big Bang Sonarqube 8.9.9-community for a while without any issues. After updating the Sonarqube image from Iron Bank on 2022-09-19, this package stopped deploying successfully. We're seeing 500/503 errors on the liveness and readiness checks and the container appears to be in a loop of attempted restarts. Attempt to get kubectl logs for the pod produces no output. After falling back to the same image/tag that was pulled from Iron Bank around 2022-08-18, Sonarqube starts up without issue.

We are running on CIS hardened CentOS 7 EC2 instances with FIPS enabled.

I tried running a docker container with the new image on an Ubuntu 22.04 VM and it works without issue.

I tried running a docker container with the new image on a similar (similar to the instances we run our RKE2 cluster on) CIS hardened CentOS 7 EC2 instance with FIPS enabled and saw some interesting behavior. Execution appears to be extremely slow for some reason as you can see from the output below. There is 13-14 minutes between the docker command to start the container and the first log output statement. When using the same image/tag from August, this period is 1-2 seconds.

[root@core-host ~]# date; docker run -it nexus.nos-lab.io:8446/ironbank/big-bang/sonarqube:8.9.9-community-bad
Wed Sep 21 22:08:26 UTC 2022
2022.09.21 22:22:04 INFO  app[][o.s.a.AppFileSystem] Cleaning or creating temp directory /opt/sonarqube/temp
2022.09.21 22:22:04 INFO  app[][o.s.a.es.EsSettings] Elasticsearch listening on [HTTP: 127.0.0.1:9001, TCP: 127.0.0.1:46609]
2022.09.21 22:22:04 INFO  app[][o.s.a.ProcessLauncherImpl] Launch process[[key='es', ipcIndex=1, logFilenamePrefix=es]] from [/opt/sonarqube/elasticsearch]: /opt/sonarqube/elasticsearch/bin/elasticsearch
2022.09.21 22:22:04 INFO  app[][o.s.a.SchedulerImpl] Waiting for Elasticsearch to be up and running
warning: no-jdk distributions that do not bundle a JDK are deprecated and will be removed in a future release