We observed OOF healthcheck failing in the integration environment (both release and staging). On investigating the logs of has-data we found out that it is caused by the failure of creating the healthcheck plan into Music stalling the progress of HAS pods.

We tried to create that healthcheck plan manually through curl but got failed with an error code of 404. Another try to fetch all the available rows inside the MUSIC table also got failed with code 404.

The log of the tomcat pod shows error in the attachment. We tried to restart the tomcat service, but it still wouldn’t work.