cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Animesh Chaturvedi (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-4316) upgrade from 3.0.4 patch1 to 4.2 failed with Unable to upgrade the database
Date Thu, 15 Aug 2013 04:59:47 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-4316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Animesh Chaturvedi resolved CLOUDSTACK-4316.
--------------------------------------------

    Resolution: Fixed

Fixing as per the commit comments
                
> upgrade from 3.0.4 patch1 to 4.2 failed with Unable to upgrade the database
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4316
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4316
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Upgrade
>    Affects Versions: 4.2.0
>         Environment: 3.0.4 patch1 to 4.2 upgrade
>            Reporter: shweta agarwal
>            Assignee: Wei Zhou
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: cloud.dmp, management-server.log
>
>
> 3.0.4 patch1 to 4.2 upgrade failed with following exception:
> Done updating router/network references
> 2013-08-14 04:17:22,087 DEBUG [upgrade.dao.Upgrade304to305] (Timer-1:null) Updating VMware
System Vms
> 2013-08-14 04:17:22,163 ERROR [cloud.upgrade.DatabaseUpgradeChecker] (Timer-1:null) Unable
to upgrade the database
> com.cloud.utils.exception.CloudRuntimeException: 3.0.5 VMware SystemVm template not found.
Cannot upgrade system Vms
>         at com.cloud.upgrade.dao.Upgrade304to305.updateSystemVms(Upgrade304to305.java:120)
>         at com.cloud.upgrade.dao.Upgrade304to305.performDataMigration(Upgrade304to305.java:69)
>         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-14 04:17:22,165 DEBUG [db.Transaction.Transaction] (Timer-1:null) Rolling back
the transaction: Time = 22282 Name =  -CloudStartupServlet$1.run:52-TimerThread.mainLoop:534-TimerThread.run:484;
called by -Transaction.rollback:898-Transaction.removeUpTo:841-Transaction.close:665-DatabaseUpgradeChecker.upgrade:293-DatabaseUpgradeChecker.check:389-ComponentContext.initComponentsLifeCycle:90-CloudStartupServlet$1.run:54-TimerThread.mainLoop:534-TimerThread.run:484
> 2013-08-14 04:17:22,186 ERROR [utils.component.ComponentContext] (Timer-1:null) System
integrity check failed. Refuse to startup
> com.cloud.utils.exception.CloudRuntimeException: Unable to upgrade the database
>         at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:291)
>         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)
> Caused by: com.cloud.utils.exception.CloudRuntimeException: 3.0.5 VMware SystemVm template
not found. Cannot upgrade system Vms
>         at com.cloud.upgrade.dao.Upgrade304to305.updateSystemVms(Upgrade304to305.java:120)
>         at com.cloud.upgrade.dao.Upgrade304to305.performDataMigration(Upgrade304to305.java:69)
>         at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:264)
>         ... 5 more

--
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

Mime
View raw message