You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sudha Ponnaganti (JIRA)" <ji...@apache.org> on 2013/08/20 23:59:53 UTC
[jira] [Commented] (CLOUDSTACK-2929) unable to upgrade from version
3.0.6.20121222035904
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13745504#comment-13745504 ]
Sudha Ponnaganti commented on CLOUDSTACK-2929:
----------------------------------------------
David,
This has been fixed for 4.2 - already tested in our lab. Can you confirm that you are ok to close it.
thanks
/sudha
> unable to upgrade from version 3.0.6.20121222035904
> ---------------------------------------------------
>
> Key: CLOUDSTACK-2929
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2929
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: centos 6.4
> Reporter: david vz
> Assignee: Alena Prokharchyk
> Priority: Blocker
> Fix For: 4.2.0
>
>
> i tried an upgrade from citrix cloudstack/platform 3.0.6 to 4.1 but the upgrade fails:
> 2013-06-11 10:18:04,038 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version befo
> re it was the version table is created
> 2013-06-11 10:18:04,046 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 3.0.6.20121222035904 Code Ver
> sion = 4.1.0
> 2013-06-11 10:18:04,054 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 3.
> 0.6.20121222035904 to 4.1.0
> 2013-06-11 10:18:04,054 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) There is no upgrade path from 3.0.6.201212
> 22035904 to 4.1.0
> 2013-06-11 10:18:04,056 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to start
> up
--
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