[
https://issues.apache.org/jira/browse/CLOUDSTACK-1801?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sudha Ponnaganti updated CLOUDSTACK-1801:
-----------------------------------------
Fix Version/s: 4.0.0
> Upgrade from 3.0.2 to 4.0.1 Fails
> ---------------------------------
>
> Key: CLOUDSTACK-1801
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1801
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: pre-4.0.0
> Environment: CentOS 6.3 64bit on both CloudStack database and
> management server, existing CloudStack 3.0.2 install.
> Reporter: John Skinner
> Labels: 3.0.2, upgrade
> Fix For: 4.0.0
>
>
> Reproduce:
> From an existing 3.0.2 install.
> 1) Shutdown management, and usage
> 2) Backup management and usage databases
> 3) Run yum update cloud-*
> 4) Start cloud-management
> Upgrade fails when checking versions.
> management-server.log snippet:
> 2013-03-25 10:20:31,160 INFO [cloud.upgrade.DatabaseIntegrityChecker]
> (main:null) Performing database integrity check
> 2013-03-25 10:20:31,211 DEBUG [cloud.upgrade.DatabaseIntegrityChecker]
> (main:null) No duplicate hosts with the same local storage found in database
> 2013-03-25 10:20:31,214 DEBUG [upgrade.dao.VersionDaoImpl] (main:null)
> Checking to see if the database is at a version before it was the version
> table is created
> 2013-03-25 10:20:31,346 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (main:null) Grabbing lock to check for database upgrade.
> 2013-03-25 10:20:31,349 DEBUG [upgrade.dao.VersionDaoImpl] (main:null)
> Checking to see if the database is at a version before it was the version
> table is created
> 2013-03-25 10:20:31,354 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (main:null) DB version = 3.0.2 Code Version = 4.0.1.20130214091207
> 2013-03-25 10:20:31,354 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (main:null) Database upgrade must be performed from 3.0.2 to
> 4.0.1.20130214091207
> 2013-03-25 10:20:31,354 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.1.20130214091207
> 2013-03-25 10:20:31,357 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.1.20130214091207
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:200)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:358)
> 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
