You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@cloudstack.apache.org by Shashi Dahal <s....@leaseweb.com> on 2013/05/03 12:01:15 UTC

issue: unable to start a stopped VM after upgrade from 2.2.14 to 4.1.0

Hi All,

After upgrade from 2.2.14 to 4.1.0, an existing VM that is stopped will not start again.
This is due to the way the storage pool is stored in the database.

This SQL query needs to be run after the upgrade, so that all old VMs can start after being stopped.

update volumes set path=SUBSTRING_INDEX(`path`, '/', -1);

I have opened a jira ticket for the same:
https://issues.apache.org/jira/browse/CLOUDSTACK-2318


This issue is discussed here: http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201206.mbox/%3C5E3DCAE61C95FA4397679425D7275D2673483EE9FD@HQ-MX03.us.teo.earth%3E

It would be great if this is done automatically by the upgrade scripts.

Cheers,
Shashi