Skip to content

Commit cf6b559

Browse files
Merge pull request #283251 from simonjj/more-qa-updates
adding provisionState:Scheduled for deletion workaround
2 parents 34032b9 + ee0ec40 commit cf6b559

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

articles/container-apps/troubleshooting.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -29,6 +29,7 @@ The following table lists issues you might encounter while using Azure Container
2929
| 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) |
3030
| 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) |
3131
| 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) |
3233

3334
## View logs
3435

@@ -212,6 +213,31 @@ If [preview features](./whats-new.md) are not available when you run `az contain
212213
az extension add --name containerapp --upgrade --allow-preview true
213214
```
214215

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
239+
```
240+
215241
## Next steps
216242
217243
> [!div class="nextstepaction"]

0 commit comments

Comments
 (0)