We have identified a code fix for this particular issue. It seems to happen almost exclusively with environments which were upgraded to vCloud Director 5.1.x, and when doing an import from vCenter which may need to change datastores on import.
↧
We have identified a code fix for this particular issue. It seems to happen almost exclusively with environments which were upgraded to vCloud Director 5.1.x, and when doing an import from vCenter which may need to change datastores on import.