ViPR Controller: Failed Create block volume - Error 1008: A component/resource with the label xxxx already exists.

Summary: When creating a Block Volume with name xxxx , ViPR Gives the Following Error Error 1008: A component/resource with the label xxxx already exists. a Stale Volume entry was found with the same name in ViPR DB that needed to be removed. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

-This might have been caused by improper Volume deletion/cleanup in the past.

When creating a Block Volume the Following Error is shown.
Error 1008: A component/resource with the label xxxx already exists.


The Order will probably fail within seconds.
 

kA2f1000000L4f7CAC_3_0

Cause

-Stale Volume Entry is in the ViPR Database and needs to be removed.
-The Volume is not seen in the Resources-Volumes.

Resolution

Steps Taken to resolve the issue (Workaround):

1-List the Volumes in the Database - Different methods can be used. (SSH / Slither Dump)

1.1-SSH to ViPR Node and Navigate to /opt/storageos/bin/
1.2-Run ./dbutils list Volume >> VolumestList.txt


2-Search for the Volume label mentioned in the Error in VolumesList.txt.
3-Once found, Confirm that the Volume doesn't have any dependencies.

3.1-Run ./dbutils show_dependencies Volume <Volume-URN>
3.2-The Above will display "if" the Volume is in an ExportGroup and in the ExportGroup group you can check if it's in an ExportMask.
3.3-If dependencies found. you can query the ExportGroup or Mask (To get more details) using the Following command - ./dbutils query ExportGroup <ExportGroup-URN> and ./dbutils query ExportMask <ExportMask-URN>  *The ExportGroup and the ExportMask URN can be obtained from the show_dependencies command mentioned in step 3.1
(Confirm that the Volume doesnot exists in real environment before doing any additional steps)

4- If not found to have any dependencies then confirm that the volume doesn't exist on the actual array and once confirmed it can be removed from ViPR DB.
5-To remove the volume, get the Volume-URN from VolumesList.txt (Created on step 1.2)
6-Run ./dbutils delete Volume <Volume-URN>
7-Rerun the failed Order.

 

Additional Information

IMPORTANT NOTE:

-It is highly recommended to engage Dell EMC ViPR Controller Technical Support as to ensure that the ViPR DB is cleaned up properly.
-Always Take a Backup of ViPR Controller before doing any alteration to ViPRs DB.
 

Article Properties
Article Number: 000065686
Article Type: Solution
Last Modified: 20 Nov 2020
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.