Skip to content

Commit 84b7ed4

Browse files
Merge pull request #279673 from rsgel/main
add troubleshooting steps for common permissions missing error
2 parents d2f89da + 8f5eaa0 commit 84b7ed4

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

articles/chaos-studio/troubleshooting.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -126,6 +126,12 @@ From the **Experiments** list in the Azure portal, select the experiment name to
126126
127127
![Screenshot that shows experiment history.](images/run-experiment-history.png)
128128
129+
Alternatively, use the REST API to obtain the experiment's execution details. Learn more in the [REST API sample article](chaos-studio-samples-rest-api.md).
130+
131+
```azurecli
132+
az rest --method post --url "https://management.azure.com/{experimentId}/executions/{executionDetailsId}/getExecutionDetails?api-version={apiVersion}"
133+
```
134+
129135
### My agent-based fault failed with the error "Verify that the target is correctly added and proper read permissions are provided to the experiment msi"
130136

131137
This error might happen if you added the agent by using the Azure portal, which has a known issue. Enabling an agent-based target doesn't assign the user-assigned managed identity to the VM or virtual machine scale set.
@@ -136,6 +142,12 @@ To resolve this problem, go to the VM or virtual machine scale set in the Azure
136142

137143
This error will happen if you try to run multiple agent faults at the same time. Today the agent only supports running a single agent-fault at a time, and will fail if you define an experiment that runs multiple agent faults at the same time.
138144

145+
### The experiment didn't start or failed immediately
146+
147+
After starting an experiment, you might see an error message like: `The long-running operation has failed. InternalServerError. The target resource(s) could not be resolved. Error Code: OperationFailedException`. Usually, this indicates that the experiment's identity doesn't have the necessary permissions.
148+
149+
To resolve this error, ensure that the experiment's system-assigned or user-assigned managed identity has permission to all resources in the experiment. Learn more about permissions here: [Permissions and security in Azure Chaos Studio](chaos-studio-permissions-security.md). For example, if the experiment targets a virtual machine, navigate to the virtual machine's identity page and assign the "Virtual Machine Contributor" role to the experiment's managed identity.
150+
139151
## Problems when setting up a managed identity
140152

141153
### When I try to add a system-assigned/user-assigned managed identity to my existing experiment, it fails to save.

0 commit comments

Comments
 (0)