-
Notifications
You must be signed in to change notification settings - Fork 267
Closed
Description
During 1.17.1 release, the Test_DeploymentStacks tests begun to fail.
(x) Failed: Failed deleting subscription deployment stack azd-stack-azdtest-l55bf66
cli.go:244: 1h0m38.879s [stdout]
cli.go:244: 1h0m38.897s [stdout] ERROR: deleting infrastructure: error deleting Azure resources: deleting resource groups: GET https://management.azure.com/subscriptions/4d042dc6-fe17-4698-a23f-ec6a8d1e98f4/providers/Microsoft.Resources/locations/eastus2/deploymentStackOperationStatus/fd8a4001-b91f-4ea6-add7-45652e1e316c
cli.go:244: 1h0m38.9s [stdout] --------------------------------------------------------------------------------
cli.go:244: 1h0m38.9s [stdout] RESPONSE 200: 200 OK
cli.go:244: 1h0m38.902s [stdout] ERROR CODE: DeploymentStackDeleteResourcesFailed
cli.go:244: 1h0m38.904s [stdout] --------------------------------------------------------------------------------
cli.go:244: 1h0m38.904s [stdout] {
cli.go:244: 1h0m38.909s [stdout] "id": "/subscriptions/4d042dc6-fe17-4698-a23f-ec6a8d1e98f4/providers/Microsoft.Resources/locations/eastus2/deploymentStackOperationStatus/fd8a4001-b91f-4ea6-add7-45652e1e316c",
cli.go:244: 1h0m38.911s [stdout] "name": "fd8a4001-b91f-4ea6-add7-45652e1e316c",
cli.go:244: 1h0m38.911s [stdout] "status": "failed",
cli.go:244: 1h0m38.911s [stdout] "error": {
cli.go:244: 1h0m38.913s [stdout] "code": "DeploymentStackDeleteResourcesFailed",
cli.go:244: 1h0m38.916s [stdout] "message": "One or more resources could not be deleted. Correlation id: '521eb68bdbd5a0c2748a19cc83e896ff'.",
cli.go:244: 1h0m38.917s [stdout] "details": [
cli.go:244: 1h0m38.917s [stdout] {
cli.go:244: 1h0m38.918s [stdout] "code": "DeploymentStackDeleteResourcesFailed",
cli.go:244: 1h0m38.931s [stdout] "message": "An error occurred while deleting resources. These resources are still present in the stack but can be deleted manually. Please see the FailedResources property for specific error information. Deletion failures that are known limitations are documented here: https://aka.ms/DeploymentStacksKnownLimitations"
cli.go:244: 1h0m38.931s [stdout] }
cli.go:244: 1h0m38.932s [stdout] ]
cli.go:244: 1h0m38.932s [stdout] }
cli.go:244: 1h0m38.932s [stdout] }
cli.go:244: 1h0m38.935s [stdout] --------------------------------------------------------------------------------
Tests are skipped for releasing and should be reviewed in the future to be re-enabled.
It might be an ongoing issue for deployment stack or maybe a test issue.