[
https://issues.apache.org/jira/browse/CLOUDSTACK-603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sailaja Mada closed CLOUDSTACK-603.
-----------------------------------
Regressed with 4.0.1 non -oss 11 build. Now upgrade went thru with no issues.
Hence closing the bug.
> Upgrade from 4.0 to 4.0.1 is not enabled
> ----------------------------------------
>
> Key: CLOUDSTACK-603
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-603
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.0.1
> Reporter: Sailaja Mada
> Priority: Blocker
> Fix For: 4.0.1
>
>
> Steps:
> 1. Install and configure 4.0 released non-oss build using Xenserver 6.0.2
> 2. Configure Advanced Zone , get all the systems ready
> 3. Perform VM operations
> 4. Stop management server
> 5. Run install.sh and execute "U" to upgrade
> 6. Start Management server
> Observation:
> Management server is not started and it failed with below exception:
> 2012-12-10 16:33:11,030 INFO [utils.component.ComponentLocator] (main:null)
> Found component: com.cloud.utils.component.SystemIntegrityChecker in
> com.cloud.upgrade.PremiumDatabaseUpgradeChecker - DatabaseUpgradeChecker
> 2012-12-10 16:33:11,031 INFO [utils.component.ComponentLocator] (main:null)
> Adding system integrity checker: DatabaseUpgradeChecker
> 2012-12-10 16:33:11,104 DEBUG [utils.crypt.EncryptionSecretKeyChecker]
> (main:null) Encryption Type: file
> 2012-12-10 16:33:11,265 INFO [cloud.upgrade.DatabaseIntegrityChecker]
> (main:null) Grabbing lock to check for database integrity.
> 2012-12-10 16:33:11,648 INFO [cloud.upgrade.DatabaseIntegrityChecker]
> (main:null) Performing database integrity check
> 2012-12-10 16:33:11,663 DEBUG [cloud.upgrade.DatabaseIntegrityChecker]
> (main:null) No duplicate hosts with the same local storage found in database
> 2012-12-10 16:33:11,666 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-12-10 16:33:11,799 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (main:null) Grabbing lock to check for database upgrade.
> 2012-12-10 16:33:11,800 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-12-10 16:33:11,803 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (main:null) DB version = 4.0.0.20121024012150 Code Version =
> 4.0.1.20121207201434
> 2012-12-10 16:33:11,804 INFO [cloud.upgrade.DatabaseUpgradeChecker]
> (main:null) Database upgrade must be performed from 4.0.0.20121024012150 to
> 4.0.1.20121207201434
> 2012-12-10 16:33:11,804 ERROR [cloud.upgrade.DatabaseUpgradeChecker]
> (main:null) There is no upgrade path from 4.0.0.20121024012150 to
> 4.0.1.20121207201434
> 2012-12-10 16:33:11,806 ERROR [utils.component.ComponentLocator] (main:null)
> Problems with running checker:DatabaseUpgradeChecker
> com.cloud.utils.exception.CloudRuntimeException: There is no upgrade path
> from 4.0.0.20121024012150 to 4.0.1.20121207201434
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:188)
> 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
