[
https://issues.apache.org/jira/browse/CLOUDSTACK-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13620837#comment-13620837
]
Tamas Monos commented on CLOUDSTACK-1151:
-----------------------------------------
2013-04-03 11:49:32,806 INFO [cloud.upgrade.DatabaseUpgradeChecker]
(main:null) DB version = 3.0.2.20120506223416 Code Version =
4.0.2.20130327104730
2013-04-03 11:49:32,807 INFO [cloud.upgrade.DatabaseUpgradeChecker]
(main:null) Database upgrade must be performed from 3.0.2.20120506223416 to
4.0.2.20130327104730
2013-04-03 11:49:32,807 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.2.20130327104730
2013-04-03 11:49:32,816 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.2.20130327104730
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)
> vmware systemVm template upgrade is missing in 4.0 upgrade
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-1151
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1151
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Template
> Affects Versions: 4.0.0
> Environment: vmware esx 4.1/5.1
> Reporter: Tamas Monos
> Assignee: Kishan Kavala
> Priority: Blocker
> Fix For: 4.0.2
>
>
> I have upgraded from 3.0.2 to 4.0.0 and the management server started and
> updated the database just fine, however the rest of the upgrade procedure
> just does not work.
> I'm running the script: "nohup cloud-sysvmadm -d 192.168.1.5 -u cloud -p
> password -c -r > sysvm.log 2>&1 &" accordingly to my environment and see in
> its log it is trying to stop/start a router.
> It stops it, then recreates the same secondary datastore (vmware) and then
> starts the same router rather than deploying the new imported systemVM
> template and creating a new one.
> It neither touches the sec-storage VM nor the console-proxy VM so new
> management system, old systemVMs.
>
> No errors during running the script no errors in the log:
> Stopping and starting 1 running routing vm(s)...
> Done restarting router(s).
--
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
