GitHub user midhunpjos created a discussion: VMware VM import fails when primary storage is a datastore cluster with multiple LUNs (LUN paths missing in DB)
We are facing an issue while importing an existing VMware VM into CloudStack. The import fails with the following error: **Storage pool for disk Hard disk 1 (460-2000) with datastore: Alletra5050-LUN010 not found in zone ID: b143173c-f373-48de-a850-be34934cbf1c** <img width="410" height="145" alt="Untitled1" src="https://github.com/user-attachments/assets/b9a05c8c-391c-4507-a9f1-679c3bffb981"; /> Environment Cloudstack Version: 4.20.0.0 Hypervisor: VMware CloudStack primary storage: Datastore Cluster Datastore cluster contains multiple LUNs (4 LUNs) In the CloudStack database, only one entry exists for the datastore cluster. There are no individual entries for the underlying LUNs and its Path belonging to this datastore cluster. But for other datastore cluster's individual LUN entries are available. The datastore/LUN paths for the individual LUNs are not present in the DB. Running syncStoragePool completes successfully but does not populate any LUN-level entries for this datastore cluster. Is there any recommended workaround to make VM import succeed in this scenario? GitHub link: https://github.com/apache/cloudstack/discussions/12561 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
