-
Cinder block storage volume does not attach to virtual machine instance
-
Cinder block storage volume does not establish an SSH connection with the 3PAR storage system
-
Unable to associate block storage driver with 3PAR storage system
-
Volume status is mismatched between CloudSystem Console and CloudSystem Portal
|
|
TIP: For additional troubleshooting information, enable console access on your Foundation base appliance using the CLI and then find the following log. To enable access, see Basic troubleshooting techniques and read the Enable console access recommendation.
See the HP 3PAR StoreServ Storage Troubleshooting Guide available from the HP Support Center web site (http://www.hp.com/go/support). |
|
|
Symptom | Possible cause and recommendation |
---|---|
3PAR iSCSI volume does not attach to VM instance |
Incorrect compute node connectivity configuration
|
When a cinder block storage volume does not attach to a VM instance, you see the following error in the |
Multiple virtual domains are defined on the 3PAR storage system
|
Symptom | Possible cause and recommendation | ||||||
---|---|---|---|---|---|---|---|
You see the error: |
The base appliance is unable to establish SSH connection with the 3PAR storage system
The base appliance is unable to establish an HTTPS connection with the 3PAR storage system
|
||||||
You see the error: |
The host key has changed
|
Symptom | Possible cause and recommendation |
---|---|
When adding or editing a block storage driver, the driver is unable to be associated with the 3PAR storage system |
Missing or incorrect user ID and password combination
Missing or invalid FQDN or IP address
|
Symptom | Possible cause and recommendation |
---|---|
When trying to delete a block storage driver, you see the message: |
The driver that you are trying to delete is associated with one or more volume types
|
Symptom | Possible cause and recommendation |
---|---|
When trying to delete a volume type you see the message: |
The volume type that you are trying to delete is associated with one or more volumes
|
Symptom | Possible cause and recommendation |
---|---|
When trying to edit a volume type, you see the message: |
The volume type that you are trying to edit was created outside of the CloudSystem Console
|
Symptom | Possible cause and recommendation |
---|---|
The current volume status that is displayed in the CloudSystem Portal is different than the status displayed in the CloudSystem Console |
The volume status displayed in the CloudSystem Console refreshes only once per hour with data from the CloudSystem Portal
|