Skip to content

Commit 0fac0e6

Browse files
authored
Added error for staging resource group
When the staging resource group is specified with the same name for two different image templates, an "InternalOperationError" error is thrown.
1 parent e70c934 commit 0fac0e6

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

articles/virtual-machines/linux/image-builder-troubleshoot.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ Microsoft.VirtualMachineImages/imageTemplates 'helloImageTemplateforSIG01' faile
105105
```
106106
#### Cause
107107

108-
In most cases, the resource deployment failure error occurs because of missing permissions.
108+
In most cases, the resource deployment failure error occurs because of missing permissions. This error may also be caused by a conflict with the staging resource group.
109109

110110
#### Solution
111111

@@ -114,6 +114,8 @@ Depending on your scenario, VM Image Builder might need permissions to:
114114
- The distribution image or Azure Compute Gallery resource.
115115
- The storage account, container, or blob that the `File` customizer is accessing.
116116

117+
Also, ensure the staging resource group name is uniquely specified for each image template.
118+
117119
For more information about configuring permissions, see [Configure VM Image Builder permissions by using the Azure CLI](image-builder-permissions-cli.md) or [Configure VM Image Builder permissions by using PowerShell](image-builder-permissions-powershell.md).
118120

119121
### Error getting a managed image

0 commit comments

Comments
 (0)