
Volume not associated with a volume type cannot be modified or deleted when the
storage driver is removed
Possible cause and recommendationSymptom
When the volume was originally created no volume type was
explicitly associated with the block storage driver.
NOTE: When a volume is created without an associated volume type and
driver, OpenStack Cinder automatically assigns a valid block storage driver
to the volume. In this situation, the volume cannot be deleted or modified if
the assigned driver is deleted. Attempting to delete or modify the volume puts
the volume in a hung state.
The volume state of “deleting” does not
change on the Volumes screens in the
CloudSystem Portal and the
CloudSystem Console.
1. To remedy the problem from the CloudSystem Portal, add the same driver
type to the volume using the same IP address. See Add Block Storage
Drivers (page 89).
2. When deleting block storage drivers, be sure to first delete the volumes
until the Block Storage Drivers overview screen in the CloudSystem Console
displays 0 in the Block storage volumes column of the Host CPG Summary.
Volume is in Error state when it is created without a block storage driver
Possible cause and recommendationSymptom
You created a volume in the CloudSystem Portal before you
created a Fibre Channel or iSCSI block storage driver in the
CloudSystem Console
• Delete volumes in an Error state using the CloudSystem Portal or
CloudSystem Console.
To prevent volumes from becoming unusable, perform the following actions
in order:
You cannot attach a volume in the
Error state to a virtual machine
instance
1. Add a block storage driver in the CloudSystem Console.
2. Add a volume type in the CloudSystem Console, and associate the volume
type with a block storage driver.
3. Create a volume in the CloudSystem Portal or using the OpenStack Cinder
CLI.
Unable to associate block storage driver with 3PAR storage system
Possible cause and recommendationSymptom
Missing or incorrect user ID and password combination
When adding or editing a block storage
driver, the driver is unable to be
1. Enter a valid user ID and password for the 3PAR storage system to which
you want to associate the driver.
associated with the 3PAR storage
system
2. If this corrects the problem an additional section is displayed on the Add
Block Storage Driver screen or the block storage driver Edit screen.
Missing or invalid FQDN or IP address
1. Enter a valid fully qualified domain name or IP address for the storage
system to which you want to associate the driver.
2. If this corrects the problem an additional section is displayed on the Add
Block Storage Driver screen or the block storage driver Edit screen.
Troubleshooting storage 169
Commentaires sur ces manuels