What does "Some instances cannot be discovered." mean.
I'm just starting out with Azure apps. I have a simple hello world app which works fine if I run it locally. I am having problems when I attempt to deploy on Azure.
Under the App Status Report, I see the following
Some apps are not healthy.
App Name: spring-app-20220826160101
Active Deployment: default
Status: Some instances cannot be discovered.
Running Instance: 1/1
Registered Instance: 0/1
Under Azure services I have
ASP-firstazureapplication-b791 (App Service plan)
first-azure-spring-app (Azure Spring Apps)
first-azure-app-dsnyder (App Service)
insight20220826 (Application Insights)
All are in the same resource group first-azure-application and the same subscription.
I attempted to upload the Java spring application, but I have the above errors. Any suggestions on where to look for the problem?
@David Snyder We apologize for the error that you are experiencing regarding your App Service Plan's instances.
This error is rather unique, and we are unable to find any past occurrences of it. As a result, we have reached out to the product group for clarification on what causes this error and how to resolve it.
My guess while we wait is that this is related to the App Service Plan not being created correctly. If so, a possible fix might be to scale your App Service Plan up/down. This would force a new instance to be allocated and maybe provide you with relief.
To scale your App Service Plan up or down:
- Navigate to your App in the Azure portal
- Select the "scale up (App Service plan) blade
- From here select a different instance and then click "apply"
- Wait 1-2 minutes and then see if this resolved the issue.
- Whether this resolved the issue or not, do not forget to scale back to your original tier to avoid any increased billing.
Once we hear back from the product group with an official response, we will update you here.
Sign in to comment
@David Snyder Can you please verify where you are getting the above error? I am not familiar with a "App Status Report" part of the Azure portal and the product group is curious as to where you are getting the error. Thanks