Just found out there is a known issue with removing datastores in and out of datastore clusters. In vCloud Director 5.1 this was working fine. vCloud Director refers to storage via storage policies (formerly profiles) so you could on-the fly change the datastore cluster structure (as long as all datastore inside had the same storage policy).
However in vCloud Director 5.5.1 if you move a datastore in or out of a datastore cluster, vCloud Director will loose it. The fix is described in KB 2075366 and involves clean up of vCloud Director database inventory data.
Advertisements
Hi Tom, thanks a lot for this post. I encountered this issue on my vCloud Director 5.5.1 platform but I didn’t find a workaround. Do I need to clean database tables each time I add a new datastore in the cluster? Do you know if this bug will be fixed in vCloud Director 5.5.2 ?
Thanks,
My understanding is that you have to clean the DB every time you add or modify a storage policy. The plan is it will get fixed in 5.5.2 (no guarantee).