Instance type change fails with Operation Start Vm wasn't completed
Applies to
- BlueXP
- Cloud Volumes ONTAP (CVO)
- Microsoft Azure
- High Availability (HA)
Issue
- License and Instance Type change is initiated from BlueXP.
- BlueXP states updated is in progress, but after waiting some time does not progress.
- Checking the BlueXP timeline, the Change License And Instance Type task fails with
Operation Start Vm wasn't completed
- Checking from BlueXP, the working environment is healthy.
- Checking from System Manager or ONTAP CLI, both nodes are online and healthy.
- From the uptime or logs, node 1 had rebooted, was taken over, and had been successfully given back by it's partner node 2.
- Node 2 has not rebooted.
- Checking in Azure Portal, node 2 is started, working normally, but the instance type has not changed.
- Attempting to change the instance type change again in BlueXP is not possible because the current type is stated to be already changed for the cluster.