You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2013/07/30 19:23:50 UTC
[jira] [Commented] (CLOUDSTACK-3936) [Upgrade from 2.2.16 to 4.2]
upgrade is not enabled from 2.2.16 to 4.2
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724106#comment-13724106 ]
Alena Prokharchyk commented on CLOUDSTACK-3936:
-----------------------------------------------
Abhinav, can you also attach cloud_usage db dump. Need it to test the fix.
> [Upgrade from 2.2.16 to 4.2] upgrade is not enabled from 2.2.16 to 4.2
> ----------------------------------------------------------------------
>
> Key: CLOUDSTACK-3936
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3936
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Upgrade
> Affects Versions: 4.2.0
> Environment: CS 2.2.16 to CS 4.2 upgrade
> Reporter: Abhinav Roy
> Assignee: Alena Prokharchyk
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: DB_DUMP_2216_cloud.sql, management-server.log
>
>
> Steps :
> ======================
> 1. Deploy a CS 2.2.15 advanced zone setup with CentOS 6.0 and MS and Xen 6.0.2 as the Host.
> 2. Do some pre-upgrade configurations.
> 3. Stop the management server and usage server.
> 4. Do the upgrade using install.sh script
> 5. run cloudstack-setup-encryption
> 6. start management server.
> Expected behaviour :
> =====================
> The DB upgrade should be successful
> Observed behaviour :
> ====================
> The DB upgrade fails with
> 2013-07-30 14:09:52,809 INFO [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker encryptionSecretKeyChecker
> 2013-07-30 14:09:52,810 DEBUG [utils.crypt.EncryptionSecretKeyChecker] (Timer-1:null) Encryption Type: file
> 2013-07-30 14:09:52,810 WARN [utils.crypt.EncryptionSecretKeyChecker] (Timer-1:null) Encryption already enabled, is check() called twice?
> 2013-07-30 14:09:52,811 INFO [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker databaseIntegrityChecker
> 2013-07-30 14:09:52,811 INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) Grabbing lock to check for database integrity.
> 2013-07-30 14:09:52,815 INFO [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) Performing database integrity check
> 2013-07-30 14:09:52,839 DEBUG [cloud.upgrade.DatabaseIntegrityChecker] (Timer-1:null) No duplicate hosts with the same local storage found in database
> 2013-07-30 14:09:52,845 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created
> 2013-07-30 14:09:52,868 INFO [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker managementServerNode
> 2013-07-30 14:09:52,869 INFO [utils.component.ComponentContext] (Timer-1:null) Running SystemIntegrityChecker DatabaseUpgradeChecker
> 2013-07-30 14:09:52,869 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Grabbing lock to check for database upgrade.
> 2013-07-30 14:09:52,871 DEBUG [upgrade.dao.VersionDaoImpl] (Timer-1:null) Checking to see if the database is at a version before it was the version table is created
> 2013-07-30 14:09:52,875 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) DB version = 2.2.16.20130528070319 Code Version = 4.2.0-SNAPSHOT
> 2013-07-30 14:09:52,876 INFO [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Database upgrade must be performed from 2.2.16.20130528070319 to 4.2.0-SNAPSHOT
> 2013-07-30 14:09:52,876 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) There is no upgrade path from 2.2.16.20130528070319 to 4.2.0-SNAPSHOT
> 2013-07-30 14:09:52,878 ERROR [utils.component.ComponentContext] (Timer-1:null) System integrity check failed. Refuse to startup
--
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