You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/container-apps/troubleshooting.md
+26Lines changed: 26 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,6 +29,7 @@ The following table lists issues you might encounter while using Azure Container
29
29
| Responses not as expected | The container app endpoint responds to requests, but the responses aren't as expected. |[Verify traffic is routed to the correct revision](#verify-traffic-is-routed-to-the-correct-revision)<br><br>[Verify you're using unique tags when deploying images to the container registry](/azure/container-registry/container-registry-image-tag-version)|
30
30
| Missing parameters error | You receive error messages about missing parameters when you run `az containerapp` commands in the Azure CLI, or run cmdlets from the `Az.App` module in Azure PowerShell. |[Verify latest version of Azure Container Apps extension is installed](#verify-latest-version-of-azure-container-apps-extension-is-installed)|
31
31
| Preview features not available |[Preview features](./whats-new.md) are not available when you run `az containerapp` commands in the Azure CLI. |[Verify Azure Container Apps extension allows preview features](#verify-azure-container-apps-extension-allows-preview-features)|
32
+
| Deleting your app or environment doesn't work | This issue is often accompanied by a message such as **provisioningState: ScheduledForDelete**. |[Manually delete the associated VNet](#manually-delete-the-vnet-being-used-by-the-azure-container-apps-environment)|
32
33
33
34
## View logs
34
35
@@ -212,6 +213,31 @@ If [preview features](./whats-new.md) are not available when you run `az contain
212
213
az extension add --name containerapp --upgrade --allow-preview true
213
214
```
214
215
216
+
217
+
## Manually delete the VNet being used by the Azure Container Apps environment
218
+
219
+
If you receive the message **provisioningState: ScheduledForDelete**, but your environment fails to actually delete, make sure to delete your associated VNet manually.
220
+
221
+
1. Identify the VNet being used by the environment you're trying to delete. Replace the \<PLACEHOLDERS\> with your values.
222
+
223
+
```azurecli
224
+
az containerapp env show --resource-group <RESOURCE_GROUP> --name <ENVIRONMENT>
225
+
```
226
+
227
+
In the output, look for `infrastructureSubnetId` and note down the VNet ID. An example VNet ID is `vNet::myVNet.id`.
228
+
229
+
2. Delete the VNet manually:
230
+
231
+
```azurecli
232
+
az network vnet delete --resource-group <RESOURCE_GROUP> --name <VNET_ID>
233
+
```
234
+
235
+
3. Delete the Azure Container Apps environment:
236
+
237
+
```azurecli
238
+
az containerapp env delete --resource-group <RESOURCE_GROUP> --name <ENVIRONMENT> --yes
0 commit comments