Starting application fails during initialization of boot layer with java.nio.file.AccessDeniedException: /jca/lib

[bryandx]

Describe the bug
We can no longer start our Spring Boot applications deployed to Azure Spring Apps. The apps fail to start with 'Exit code 1'. The console output from the application has:
Error occurred during initialization of boot layer
java.lang.module.FindException: java.nio.file.AccessDeniedException: /jca/lib

What I noticed is if we disable loading a Certificate into the trust store (attached screenshot), the application will start. However, we need the Certificate loaded into the trust store so our applications can access resources utilizing the Certificate so this option isn't a viable solution.

We first ran into the error on 11/8/2023 around 2pm EST. We have multiple applications running in Azure Spring. However, we're very afraid that if we restart them, they will fail with this error because we load the same Certificate into the trust store of each application. It appears that something has changed within Azure (Azure Spring or Azure Key Vault) as we haven't changed anything with our applications for a few weeks.

To Reproduce
Steps to reproduce the behavior:

1. Create a Spring Boot application deployment in Azure Spring which relies on a Certificate in the trust store
2. Add the Certificate to the application and check 'Load into trust store'
3. Start the Spring Boot application deployment
4. Start should fail with exit code 1

Expected behavior
Application starts successfully

Screenshots

Can we contact you for additional details? Y/N
Y

[haoozhang]

@bryandx Thanks for reaching up us.
Recently, the underlying AKS platform for Azure Spring Apps reported a volume mount issue that affected certain Azure Spring Apps services. A hotfix is currently being released to address this issue. However, we have observed that some service instances may still require manual intervention for complete recovery.
If your app is still experiencing issues or if you require immediate assistance to resolve the issue promptly, please open an Azure Support ticket. This will engage the backend team to assist you in resolving the issue.