nvazquez commented on issue #8712: URL: https://github.com/apache/cloudstack/issues/8712#issuecomment-1976654413
Hi @omurozlu - I have tested 4.19.0 creating a VM with a ROOT volume on a datastore cluster, unmanaging it and import it back and it succeeds. I have checked your logs and the images you have shared and I think the problem is that the datastore cluster in which the ROOT volume of the VM is located, is not added to CloudStack. From the cmk output, CloudStack is looking for datastore FA360-DS02-ESX: ```` "Storage pool for disk Hard disk 1(123-2000) with datastore: FA360-DS02-ESX not found in zone ID: 3e34a0b7-ba5e-44f1-ab7a-8598549095dc" ```` However, from the images above, I only see one datastore with name FA360-DS01-ESX. Can you double check the names on vCenter and CloudStack? In case you have renamed the datastore on vCenter, you should rename it as well on CloudStack for them to match -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
