Cannot Delete Corrupted Storage Repository Using "repos.py -d"
(Doc ID 1089113.1)
Last updated on MARCH 19, 2020
Applies to:Oracle VM - Version 2.2.1 and later
Oracle Cloud Infrastructure - Version N/A and later
Information in this document applies to any platform.
You have created a pool with 2 storage repositories. If one storage repository is destroyed (by a corrupted partition or similar reason), you would want to remove the corrupted repository from the configuration.
The repository list command will show error for the specific storage repository:
[ ] 1caf5f61-0246-4965-b54f-c0262a4c570b => ERROR
[ * ] 3139dae2-6763-4788-bd5f-cac304f77678 => /dev/sda5
In this case you may not be able to remove the bad repository using repos -d. This may have been caused many other operations (adding a new storage repository, import vm/iso etc.) failed. After attempting to delete:
[ DEL ] 1caf5f61-0246-4965-b54f-c0262a4c570b => /dev/sdb1
trying to initialize the repositories fail:
Error: errcode=00000, errmsg=Unexpected error: errcode=50006, errmsg=Do
'clusterm_init_sr' on servers ('ca-ostest227.us.oracle.com') failed.
File "/opt/ovs-agent-2.3/OVSSiteCluster.py", line 648, in _cluster_setup
File "/opt/ovs-agent-2.3/OVSXCluster.py", line 344, in _check
One or more storage repositories get corrupted.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document