You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/chaos-studio/troubleshooting.md
+32Lines changed: 32 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,6 +54,38 @@ Agent-based faults may fail for a variety of reasons related to missing prerequi
54
54
* On either Linux or Windows VMs, the user-assigned managed identity provided during agent-based target enablement must also be added to the virtual machine.
55
55
* On either Linux or Windows VMs, the system-assigned managed identity for the experiment must be granted Reader role on the VM (seemingly elevated roles like Virtual Machine Contributor do not include the \*/Read operation that is necessary for the Chaos Studio agent service to read the microsoft-agent target proxy resource on the virtual machine).
56
56
57
+
### Chaos agent won't install on Virtual Machine Scale Set (VMSS)
58
+
59
+
Installing the Chaos agent on a VMSS may fail with without showing an error if the VMSS upgrade policy is set to **Manual**. To check the VMSS upgrade policy:
60
+
61
+
1. Login to Azure Portal.
62
+
1. Select **Virtual Machine Scale Set (VMSS)**.
63
+
1. From the left pane menu, choose **Upgrade policy**.
64
+
1. Check the **Upgrade mode** to see if it's set to **Manual - Existing instances must be manually upgraded**.
65
+
66
+
If the Upgrade policy is set to **Manual**, you can manually upgrade your VMSS instances so that you'll be able to install the Chaos agent.
67
+
68
+
#### Upgrade instances from Azure Portal
69
+
70
+
You can upgrade you VMSS instances from Azure Portal:
71
+
72
+
1. Login to Azure Portal.
73
+
1. Select **Virtual Machine Scale Set (VMSS)**.
74
+
1. From the left pane menu, choose **Instances**.
75
+
1. Select all instances and click **Upgrade**.
76
+
77
+
#### Upgrade instances with the Azure CLI
78
+
79
+
You can upgrade your VMSS instances with Azure CLI:
80
+
81
+
- From the Azure CLI, use `az vmss update-instances` to manually upgrade your instances:
82
+
83
+
```azurecli
84
+
az vmss update-instances --resource-group myResourceGroup --name myScaleSet --instance-ids {instanceIds}
85
+
```
86
+
87
+
For more information see [How to bring VMs up-to-date with the latest scale set model](/azure/virtual-machine-scale-sets/virtual-machine-scale-sets-upgrade-scale-set#how-to-bring-vms-up-to-date-with-the-latest-scale-set-model)
88
+
57
89
### AKS Chaos Mesh faults fail
58
90
AKS Chaos Mesh faults may fail for a variety of reasons related to missing prerequisites:
59
91
* Chaos Mesh must first be installed on the AKS cluster before using the AKS Chaos Mesh faults. Instructions can be found in the [Chaos Mesh faults on AKS tutorial](chaos-studio-tutorial-aks-portal.md#set-up-chaos-mesh-on-your-aks-cluster).
0 commit comments