Skip to content

Commit 247a2cf

Browse files
authored
Merge pull request #101238 from DCtheGeek/dmc-bp-assigndelto
Add details about assignment timeout
2 parents 4d0d2ac + 0a30532 commit 247a2cf

File tree

1 file changed

+23
-3
lines changed
  • articles/governance/blueprints/troubleshoot

1 file changed

+23
-3
lines changed

articles/governance/blueprints/troubleshoot/general.md

Lines changed: 23 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,13 +1,13 @@
11
---
22
title: Troubleshoot common errors
33
description: Learn how to troubleshoot issues creating, assigning, and removing blueprints such as policy violations and blueprint parameter functions.
4-
ms.date: 11/22/2019
4+
ms.date: 01/15/2020
55
ms.topic: troubleshooting
66
---
77
# Troubleshoot errors using Azure Blueprints
88

9-
You may run into errors when creating or assigning blueprints. This article describes various errors
10-
that may occur and how to resolve them.
9+
You may run into errors when creating, assigning, or removing blueprints. This article describes
10+
various errors that may occur and how to resolve them.
1111

1212
## Finding error details
1313

@@ -72,6 +72,26 @@ treat the value as a string when processing the blueprint. Blueprints then place
7272
the artifact allowing it to be dynamic as expected. For more information, see
7373
[Syntax and expressions in Azure Resource Manager templates](../../../azure-resource-manager/templates/template-expressions.md).
7474

75+
## Delete errors
76+
77+
### <a name="assign-delete-timeout"></a>Scenario: Assignment deletion timeout
78+
79+
#### Issue
80+
81+
Deletion of a blueprint assignment doesn't complete.
82+
83+
#### Cause
84+
85+
A blueprint assignment may become stuck in a non-terminal state when deleted. This state is caused
86+
when resources created by the blueprint assignment are still pending deletion or don't return a
87+
status code to Azure Blueprints.
88+
89+
#### Resolution
90+
91+
Blueprint assignments in a non-terminal state are automatically marked **Failed** after a _6 hour_
92+
timeout. Once the timeout has adjusted the state of the blueprint assignment, the delete can be
93+
retried.
94+
7595
## Next steps
7696

7797
If you didn't see your problem or are unable to solve your issue, visit one of the following

0 commit comments

Comments
 (0)