I removed the stuck jobs, changed status to Ready and restarted the management servers. This has got my Vm back on line.
CONFIDENTIAL: This electronic mail, including any attachment(s) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify me immediately by reply email so that I may correct my internal records. Please then delete the original message (including any attachments) in its entirety. Thank you. -----Original Message----- From: Matthew Midgett [mailto:clouds...@trick-solutions.com.INVALID] Sent: Monday, November 10, 2014 10:48 AM To: users@cloudstack.apache.org Subject: Root volume stuck in migrating state Xenserver 6.2 and ACS 4.4.0 Cause: shutdown VM, made snapshot, Deleted snapshot. Tried to dl the root volume and it error about not being able to copy from primary to secondary storage. Now it's stuck in a migrating state and will not start back up. Not sure what the heck caused this. I've trashed the SSVM and waited for it to come back on line, restarted management agents. Thinking about shutting down management and manually changing the DB to ready and then starting things back up. I can dl iso to sec storage and create new servers just fine. How can I debug not being able to dl a root volume. I think this is also causing me not to be able to deploy a template from Nux and Ian. My Sec storage is accessible and had plenty of room left. Thanks Matthew Midgett CONFIDENTIAL: This electronic mail, including any attachment(s) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic email or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify me immediately by reply email so that I may correct my internal records. Please then delete the original message (including any attachments) in its entirety. Thank you.