
Possible cause and recommendationSymptom
(/var/log/nova/compute.log) and the appliance
(/var/log/cinder/volume.log).
2. Also check the /var/log/ciDebugLogxxx.log and
/var/cinder/scheduler.log files for possible clues.
3. Search foran error in the log files to determine the issue.
4. If you still are unable to determine the problem, forward the log files to
HP.
Cinder block storage volume does not establish an SSH connection with the 3PAR
storage system
Possible cause and recommendationSymptom
The base appliance is unable to establish SSH connection with
the 3PAR storage system
You see the error:
3PAR_SSH_CONNECTION_FAILURE
1. Retry the request.
2. If the error persists, verify that SSH connections to the 3PAR storage system
can be established from the base appliance, and then try the request
again.
The base appliance is unable to establish an HTTPS connection
with the 3PAR storage system
1. Retry the request.
2. If the error persists, re-import the 3PAR SSL certificate into the base
appliance, and then retry the request.
The host key has changed
NOTE: The host key can change when upgrading firmware, or if
CloudSystem Console security is compromised.
1. Manually verify that the correct 3PAR SSH host key is installed on the
base appliance.
You see the error:
3PAR_SSH_CONNECTION_KEY_MISMATCH
_FAILURE
Specifying a device already in use causes an error when attaching a volume
Possible cause and recommendationSymptom
The guest operating system allocates the next available device
name to attach to the volume
• If you specify a device already in use
or an ESX reserved device
(/dev/vdh, /dev/sdh, /dev/vdp,
• Using the CloudSystem Portal, you must specify a device. For example,
enter /dev/sdc for ESX and /dev/vdc for KVM.
and /dev/sdp), the operation does
not succeed and the volume is not
attached to the instance
NOTE: Do not specify a device that is currently in use. However, the
device you specify is not necessarily the device that is attached.
• If you specify a device not in use, the
specified device is not necessarily
attached
When the volume is attached, log in to the deployed instance operating
system and view the device information for the instance. The volume details
in the CloudSystem Portal reflect the device initially used while attaching
the volume, but do not necessarily reflect the final device as seen by the
operating system.
• Using the the OpenStack CLI, use the “auto” option to allow Nova to
automatically select the device name. For example:
nova volume-attach <instance-ID> volume auto
• Using the OpenStack API, use the “device null” option.
168 Troubleshoot resource configuration
Komentarze do niniejszej Instrukcji