No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Backend Storage Pool Does Not Exist

Publication Date:  2019-05-06 Views:  108 Downloads:  0
Issue Description

A user failed to apply for an EVS disk or ECS through the ManageOne operation plane. The user opens the logs collected by the g-ray service and finds that an error code shown in the figure below is displayed for the cinder-volume service (cinder-volume-cascaded service for FusionCloud Type I).


The user clicks the error code. A dialog box is displayed, showing the message "Bad or unexpected response from the storage volume backend API: Can not get pool info. pool: test_TypeI_can_delete."



The reason is that the storage pool name configured by the user does not exist on the storage device. As a result, the cinder-volume service cannot find the corresponding storage pool when the user applies for an EVS disk or ECS.



Handling Process

The reason is that the storage pool name configured by the user does not exist on the storage device. As a result, the cinder-volume service cannot find the corresponding storage pool when the user applies for an EVS disk or ECS.

Solution

1.       Contact the administrator to log in to the FusionSphere OpenStack web client (FusionSphere OpenStack web client at the cascaded layer for FusionCloud Type I). Then, choose Configuration > Manage Resource Pool > KVM, as shown in the figure below.


1.       Click the setting button of the storage cluster for the ECS used by the user. (If there are multiple storage clusters, see Finding the cinder-volume-kvm Service on the Page for Applying for ECSs to search for the target cinder-kvm service, as shown in the figure below.


1.       In the Configure Parameter area, check the REST URL and name of the storage pool. Set Storage Pool Name to the name of a storage pool available on the storage device. After the configuration is completed, contact the user to provision services again.



Example: How do I check the storage pool on the OceanStor V3?

                         i.          Log in to the OceanStor DeviceManager and choose Provisioning > Storage Pool. Then, check the information about all storage pools, as shown in the following figure.



                         i.          Change the storage resource pool name configured for the cinder-volume-kvm service to the name of a storage pool that exists on the storage device but is not used.






Suggestions

If a storage pool does not exist, the possible cause is that an error occurs when the user configures the storage cluster or the user deletes the storage pool from the storage device.

END