Abhinav Roy created CLOUDSTACK-4070:
---------------------------------------
Summary: [Upgrade][2.2.14 to 4.2] upgrade from 2.2.14 to 4.2 is
failing with 4.0 VMware SystemVm template not found. Cannot upgrade system Vms
Key: CLOUDSTACK-4070
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4070
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Upgrade
Affects Versions: 4.2.0
Reporter: Abhinav Roy
Priority: Blocker
Fix For: 4.2.0
DB Upgrade from 2.2.14 to 4.2 is failing with
2013-08-05 14:58:30,815 ERROR [cloud.upgrade.DatabaseUpgradeChecker]
(Timer-1:null) Unable to upgrade the database
com.cloud.utils.exception.CloudRuntimeException: 4.0 VMware SystemVm template
not found. Cannot upgrade system Vms
at
com.cloud.upgrade.dao.Upgrade302to40.updateVmWareSystemVms(Upgrade302to40.java:126)
at
com.cloud.upgrade.dao.Upgrade302to40.performDataMigration(Upgrade302to40.java:67)
at
com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:264)
at
com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:389)
at
com.cloud.utils.component.ComponentContext.initComponentsLifeCycle(ComponentContext.java:90)
at
com.cloud.servlet.CloudStartupServlet$1.run(CloudStartupServlet.java:54)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
2013-08-05 14:58:30,816 DEBUG [db.Transaction.Transaction] (Timer-1:null)
Rolling back the transaction: Time = 1057 Name =
-CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484;
called by
-Transaction.rollback:896-Transaction.removeUpTo:839-Transaction.close:663-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
2013-08-05 14:58:30,818 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
