Abhinav Roy created CLOUDSTACK-90:
-------------------------------------
Summary: Upgrade from CloudStack 3.0.2 to ASF 4.0 Failed !!
Key: CLOUDSTACK-90
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-90
Project: CloudStack
Issue Type: Bug
Components: Install and Setup
Affects Versions: pre-4.0.0
Environment: Management Sever : Rhel 6.2
CloudStack 3.0.2 Build : CloudStack-3.0.2-1-rhel6.2.tar.gz
[Git Revision: 26c4eade7f9970efd8eee76bdeb9f678c2d544e4
Git URL: ssh://[email protected]/var/lib/git/cloudstack-oss]
ASF 4.0 Build : CloudStack-oss-4.0.59-rhel6.3.tar.gz
[Git Revision: 03df2fa9dd45c938f72cd1866044b09d1b0cc978
Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git]
Reporter: Abhinav Roy
Priority: Blocker
Fix For: pre-4.0.0
Steps :
===============================
1. Install CloudStack 3.0.2 on Rhel 6.2 and deploy Advanced zone config.
2. Create a VM instance.
3. Stop the management server.
4. Take DB backup.
5. Upgrade to ASF 4.0
6. Start the management server .
Expected Behaviour
================================
The upgrade should be successful.
Observed Behaviour
================================
The upgrade failed with the following errors :
2012-09-13 16:06:48,238 DEBUG [cloud.upgrade.DatabaseIntegrityChecker]
(main:null) No duplicate hosts with the same local storage found in database
2012-09-13 16:06:48,243 DEBUG [upgrade.dao.VersionDaoImpl] (main:null) Checking
to see if the database is at a version before it was the version table is
created
2012-09-13 16:06:48,399 INFO [cloud.upgrade.DatabaseUpgradeChecker]
(main:null) Grabbing lock to check for database upgrade.
2012-09-13 16:06:48,401 DEBUG [upgrade.dao.VersionDaoImpl] (main:null) Checking
to see if the database is at a version before it was the version table is
created
2012-09-13 16:06:48,406 INFO [cloud.upgrade.DatabaseUpgradeChecker]
(main:null) DB version = 3.0.2.20120506222956 Code Version =
4.0.59.20120908055459
2012-09-13 16:06:48,407 INFO [cloud.upgrade.DatabaseUpgradeChecker]
(main:null) Database upgrade must be performed from 3.0.2.20120506222956 to
4.0.59.20120908055459
2012-09-13 16:06:48,407 ERROR [cloud.upgrade.DatabaseUpgradeChecker]
(main:null) The end upgrade version is actually at 4.0.0 but our management
server code version is at 4.0.59.20120908055459
2012-09-13 16:06:48,411 ERROR [utils.component.ComponentLocator] (main:null)
Problems with running checker:DatabaseUpgradeChecker
com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is
actually at 4.0.0 but our management server code version is at
4.0.59.20120908055459
at
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:193)
at
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:351)
at
com.cloud.utils.component.ComponentLocator.runCheckers(ComponentLocator.java:273)
at
com.cloud.utils.component.ComponentLocator.parse(ComponentLocator.java:245)
at
com.cloud.utils.component.ComponentLocator.getLocatorInternal(ComponentLocator.java:836)
at
com.cloud.utils.component.ComponentLocator.getLocator(ComponentLocator.java:874)
at
com.cloud.utils.component.ComponentLocator.getComponent(ComponentLocator.java:416)
at
com.cloud.utils.component.ComponentLocator.getComponent(ComponentLocator.java:409)
at
com.cloud.servlet.CloudStartupServlet.init(CloudStartupServlet.java:44)
at javax.servlet.GenericServlet.init(GenericServlet.java:212)
at
org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1173)
at
org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:993)
at
org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4187)
at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4496)
at
org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791)
at
org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:526)
at
org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1041)
at
org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:964)
at
org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:502)
at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1277)
at
org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:321)
at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1053)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:722)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045)
at
org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at
org.apache.catalina.core.StandardService.start(StandardService.java:516)
at
org.apache.catalina.core.StandardServer.start(StandardServer.java:710)
at org.apache.catalina.startup.Catalina.start(Catalina.java:593)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
--
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
