cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-2090) Upgrade from version 4.0.1 to version 4.0.2 triggers the 4.0.0 to 4.0.1.
Date Thu, 18 Apr 2013 14:27:15 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13635200#comment-13635200
] 

ASF subversion and git services commented on CLOUDSTACK-2090:
-------------------------------------------------------------

Commit c898b72b33f761c21ad2898de9a042057fef30c3 in branch refs/heads/4.0 from Hugo Trippaers
<htrippaers@schubergphilis.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c898b72 ]

CLOUDSTACK-2090 Fix upgradepath from 4.0.1 to 4.0.2

                
> Upgrade from version 4.0.1 to version 4.0.2 triggers the 4.0.0 to 4.0.1.
> ------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2090
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2090
>             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.2
>            Reporter: Hugo Trippaers
>            Assignee: Hugo Trippaers
>             Fix For: 4.0.2
>
>
> See log except:
> 2013-04-18 14:06:59,318 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Grabbing
lock to check for database upgrade.
> 2013-04-18 14:06:59,323 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-04-18 14:06:59,331 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) DB version
= 4.0.1.20130213113444 Code Version = 4.0.2.20130417161502
> 2013-04-18 14:06:59,332 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Database
upgrade must be performed from 4.0.1.20130213113444 to 4.0.2.20130417161502
> 2013-04-18 14:06:59,333 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Running
upgrade Upgrade40to401 to upgrade from 4.0.0-4.0.1 to 4.0.1
> 2013-04-18 14:06:59,375 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Running
upgrade Upgrade401to402 to upgrade from 4.0.0-4.0.1 to 4.0.2
> 2013-04-18 14:06:59,409 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Cleaning
upgrades because all management server are now at the same version
> 2013-04-18 14:06:59,415 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Upgrading
to version 4.0.1...
> 2013-04-18 14:06:59,415 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Cleanup
upgrade Upgrade40to401 to upgrade from 4.0.0-4.0.1 to 4.0.1
> 2013-04-18 14:06:59,430 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Upgrade
completed for version 4.0.1
> 2013-04-18 14:06:59,445 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Upgrading
to version 4.0.2...
> 2013-04-18 14:06:59,449 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Cleanup
upgrade Upgrade401to402 to upgrade from 4.0.0-4.0.1 to 4.0.2
> 2013-04-18 14:06:59,454 DEBUG [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Upgrade
completed for version 4.0.2

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