Hi, I'm happy and can confirm this workaround sorted my problem.
Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk Follow us on Twitter: www.twitter.com/veberhost Follow us on Facebook: www.facebook.com/veberhost -----Original Message----- From: Tamas Monos [mailto:[email protected]] Sent: 13 June 2012 12:04 To: [email protected] Subject: Question: Resource [volume: x] unreachable, not re-creatable Hi, Problem: I have come across this error the other day mentioned in the subject. What happened is around a month ago someone deployed VMs from a template. That template have been removed from cloudstack so does not exist anymore as template, a new template replaces it. Those virtual machines were set to use the new template ID so the GUI shows the new template name under the VM details however the ROOT Volumes of the VMs in the DB still carry the old template_id which was deleted. So when those VMs are stopped and I want to start them CS is saying: Vol[xx|vm=yy|ROOT] of VM[User|i-zz-vv-VM] is READY, but template ids don't match, let the planner reassign a let the planner reassign a new pool Volume Vol[xx|vm=yy|ROOT] is not re-creatable! Cannot recreate on storagepool: Pool[www|VMFS] Unable to contact resource. Volume is not re-creatable, Unable to create Vol[xx|vm=yy|ROOT] Proposed Resolution: As the template was still on the primary storage used as a ROOT disk by the other VMs I have exported that into a template and re-imported into CS (found out its ID from the template_spool_ref table). I have deployed it into a fresh VM and it worked, the same system came up so the template is good. After that I went into the DB and updated the "volumes" and "vm_instance" tables to use the new template_id which I've just imported instead of the old one which does not exist and updated the "template_spool_ref" with the new ID pointing to the old (original) disk. Question: I have not stopped/started any of the VMs in question as they customer servers are in production. I have backups/snapshots/templates for safety however I want to prevent CS from re-creating any ROOT volumes as I'm afraid that would kill the DATA on the ROOT disk. Are there any other references in other tables I should be aware of? Would this scenario work? Any help appreciated. Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk<http://www.veber.co.uk/> Follow us on Twitter: www.twitter.com/veberhost<http://www.twitter.com/veberhost> Follow us on Facebook: www.facebook.com/veberhost<http://www.facebook.com/veberhost>
