Could Not Update Passwords; Vsa Volumes Did Not Stabilize In 10 Minutes; Vm <Name> Did Not Power Off - <Error Msg; Problem Finding Original Vcenter Cluster - HP Hyper Converged 380 Installation Manual

•
Perform a manual update by referring to HPE Helion CloudSystem 9.0 Installation Guide located on
the Hewlett Packard Enterprise website (http://www.hpe.com/info/CloudSystem/docs).

Could not update passwords

Symptom
Could not update the administrator password for CloudSystem.
Action
Hewlett Packard Enterprise recommends that you back up your system and take a snapshot of
CloudSystem before changing. If the process fails, see HPE Helion CloudSystem 9.0 Administrator Guide
for the manual update process or to restore to a previous snapshot. The guide is located on the Hewlett
Packard Enterprise website (http://www.hpe.com/info/CloudSystem/docs).
VSA volumes did not stabilize in 10 minutes...cannot continue
Symptom
VSA VM cannot be powered off.
Explanation
Before creating the CS9 Management cluster and moving the management VM to this cluster, the utility
powers off the VSA VM on the management node. If the VSA volumes are pending activity, the VM cannot
be powered off until the VSA storage reaches a stable state.
Action
For more information, see "Trouble migrating host to management cluster."
VM <name> did not power off - <error msg>
Symptom
VSA VM could not be powered off on the management node.
Explanation
Before creating the CS9 Management cluster and moving the management VM to this cluster, the VSA
VM must be powered off on the management node. If the VSA volume could not be powered off, then the
VSA volume has some pending activity.
Action
The VM will have to be powered off manually. For more information, see "Trouble migrating host to
management cluster."

Problem finding original vCenter cluster

Symptom
Installation utility is not able to locate original cluster name.
Explanation
When trying to create the CS9Compute cluster and migrate all future compute nodes to this cluster, if the
installation utility cannot find the original cluster name as specified during the OneView InstantOn
deployment, it cannot proceed.
Action
Troubleshooting 83