Closed felipmiguel closed 1 year ago
The issue seems related to the application insights version attached to the application as seems to refer to azure-spring-boot-2.3.0.jar instead of azure-spring-boot.3.0.0
I created a new Azure Spring Apps cluster and deployed again the application using azure/spring-apps-deploy
Github action and this time it works. I think the issue happens with existing clusters, not new ones. My environment was for testing, but this solution (create a new cluster) cannot be applied in production environments.
After reviewing the solution I realized that the version deployed with azure cli and the version deployed with github actions are not exactly the same. The failing version included an old version for one of the dependencies. Removing that dependency fixed the issue.
Describe the bug GitHub Action azure/spring-apps-deploy@v1 fails when targeting a Java 17 Spring Boot 3 application. The same application works fine if deployed from Azure cli (version 2.44)
To Reproduce Steps to reproduce the behavior:
az spring app logs
commandAn example can be found here https://github.com/felipmiguel/spring-petclinic-microservices/blob/3.0.0/.github/workflows/action.yml Failing action:
Expected behavior The application should be deployed and started normally. The same application has been deployed using the following command and it works:
Screenshots
Here the failed application logs:
Additional context Also created an issue here https://github.com/Azure/spring-apps-deploy/issues/22
Can we contact you for additional details? Y/N
If yes, please send us your contact information to AzureSpringCloud-Talk@service.microsoft.com and include the issue number in the email title.