Shashi Dahal created CLOUDSTACK-2318:
----------------------------------------
Summary: upgrade from 2.2.14 -> 4.1.0 : unable to start an
existing running vm after stopping it manually
Key: CLOUDSTACK-2318
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2318
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: KVM
Affects Versions: 4.1.0
Environment: CentOS 6.4 .. 2.6.32-358.2.1.el6.x86_64 #1 SMP Wed Mar 13
00:26:49 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Shashi Dahal
Priority: Minor
Fix For: 4.1.0
Hi,
I was able to successfully upgrade from 2.2.14 to 4.1.0
Successfully in the sense that the upgrade steps worked without issues.
For the VMS that were running before the upgrade, I could do the following
reboot
stop
change password - it gave a new password
I could not start an existing VM because the way the paths are in the database
is different.
I had to apply this database fix to get an existing stopped VM to start state.
update volumes set path=SUBSTRING_INDEX(`path`, '/', -1);
This is discussed here:
http://mail-archives.apache.org/mod_mbox/incubator-cloudstack-dev/201206.mbox/%[email protected]%3E
It would be great if this can be checked/included in the 4.1.0 release also.
Thanks,
Shashi
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
