Troubleshooting
If your issue isn’t listed below, report it in our Issues log.
Errors like Parameter cannot be processed because the parameter name 'i' is ambiguous... usually indicate an outdated module. Update and retry.
If issues persist, note that modules installed in PowerShell 5.X override PowerShell 7.X (pwsh) modules. Uninstall from PS 5.X first.
Follow these steps to ensure you have a working environment:
- Update the latest PowerShell Core / 7.X (
pwsh) version. - Open a PS (PowerShell 5.1) terminal. You may need to be an administrator to do this.
- Run
Uninstall-PSResource -Name ALZ, then runGet-InstalledPSResource -Name ALZ - If the previous command shows a version of the module is still installed, then repeat the previous step until you no longer see an installed version.
- Open a
pwsh(PowerShell 7.X) terminal. - Run
Uninstall-PSResource -Name ALZ, then runGet-InstalledPSResource -Name ALZ - If the previous command shows a version of the module is still installed, then repeat the previous step until you no longer see an installed version.
- Run
Install-PSResource -Name ALZ
You should now be able to successfully run the Deploy-Accelerator command and continue.
Error: 422 This group cannot be deleted because it contains runners...
Runners don’t auto-delete when container instances are removed; they show offline for 14 days. Manually delete runners from the Runner Group in GitHub UI, then re-run destroy.
This only affects Enterprise licensing with Runner Groups. See: https://docs.github.com/en/actions/hosting-your-own-runners/managing-self-hosted-runners/removing-self-hosted-runners
This occurs when a region claims availability zone support but doesn’t support it for Azure Container Instances.
Workaround: add the following to your input config file:
# GitHub
runner_container_zone_support: false
# Azure DevOps
agent_container_zone_support: false
╷
│ Error: creating Container Group (Subscription: "**754f66-****-4f64-****-221f0174ad4**"
│ Resource Group Name: "rg-alz-r14c67r424-agents-swedencentral-001"
│ Container Group Name: "aci-alz-r14c67r424-swedencentral-002"): polling after ContainerGroupsCreateOrUpdate: polling failed: the Azure API returned the following error:
│
│ Status: "Failed"
│ Code: "Failed"
│ Message: "The requested resource is not available in the location 'swedencentral' at this moment. Please retry with a different resource request or in another location. Resource requested: '2' CPU '4' GB memory 'Linux' OS"
│ Activity Id: ""
│
│ ---
│
│ API Response:
│
│ ----[start]----
│ {"id":"/subscriptions/**754f66-****-4f64-****-221f0174ad4**/resourceGroups/rg-alz-r14c67r424-agents-swedencentral-001/providers/Microsoft.ContainerInstance/containerGroups/aci-alz-r14c67r424-swedencentral-002","status":"Failed","startTime":"2024-11-29T11:15:39.9940663Z","properties":{"events":[{"count":1,"firstTimestamp":"2024-11-29T11:15:41.1163736Z","lastTimestamp":"2024-11-29T11:15:41.1163736Z","name":"InsufficientCapacity.","message":"The requested resource is not available in the location 'swedencentral' at this moment. Please retry with a different resource request or in another location. Resource requested: '2' CPU '4' GB memory 'Linux' OS","type":"Warning"}]},"error":{"message":"The requested resource is not available in the location 'swedencentral' at this moment. Please retry with a different resource request or in another location. Resource requested: '2' CPU '4' GB memory 'Linux' OS"}}
│ -----[end]-----
│
│
│ with module.azure.azurerm_container_group.alz["agent_02"],
│ on ../../modules/azure/container_instances.tf line 1, in resource "azurerm_container_group" "alz":
│ 1: resource "azurerm_container_group" "alz" {
│
╵
Error: Failed to delete resource - when destroying the Platform landing zone on the module.management_groups.module.management_groups.azapi_resource.subscription_(platform subscription) resource
If you are trying to destroy your Platform landing zone and you see three errors like the below, it is because you don’t have permissions on the management group that it is trying to move the subscriptions to.
This is the default management group, in most cases Tenant Root Group. If you didn’t use Tenant Root Group as your root parent management group for the deployment, you will recall that you had to move the platform subscriptions under the management group you defined. The bootstrap only applied permissions to that management group and therefore has no permissions on your default management group.
You have two options to resolve this:
- Manually move the subscriptions back to the default management group or your chosen root management group before destroying the Platform landing zone.
- Change the default management group for your tenant to the management group you used for the Platform landing zone.
╷
│ Error: Failed to delete resource
│
│ deleting Resource: (ResourceId
│ "/providers/Microsoft.Management/managementGroups/levelup-identity/subscriptions/**754f66-****-4f64-****-221f0174ad4**"
│ / Api Version "2023-04-01"): DELETE
│ https://management.azure.com/providers/Microsoft.Management/managementGroups/levelup-identity/subscriptions/**754f66-****-4f64-****-221f0174ad4**
│ --------------------------------------------------------------------------------
│ RESPONSE 400: 400 Bad Request
│ ERROR CODE: BadRequest
│ --------------------------------------------------------------------------------
│ {
│ "error": {
│ "code": "BadRequest",
│ "message": "Permission to write and delete on resources of type 'Microsoft.Authorization/roleAssignments' is required on the subscription or its ancestors.",
│ "details": "Subscription ID: '/subscriptions/**754f66-****-4f64-****-221f0174ad4**'"
│ }
│ }
│ --------------------------------------------------------------------------------
│
╵