Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 5 Aug 2013 22:42:48 +0000 (UTC)
From: "Animesh Chaturvedi (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12644573.1366886183507.4480.1375742568660@arcas>
In-Reply-To: <JIRA.12644573.1366886183507@arcas>
References: <JIRA.12644573.1366886183507@arcas>
Subject: [jira] [Updated] (CLOUDSTACK-2183) Database upgrade from 3.0.2 to
 4.0.1 failed
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Animesh Chaturvedi updated CLOUDSTACK-2183:
-------------------------------------------

    Fix Version/s: 4.0.1
    
> Database upgrade from 3.0.2 to 4.0.1 failed
> -------------------------------------------
>
>                 Key: CLOUDSTACK-2183
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2183
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.0.1
>         Environment: CloudStack 3.0.2 upgrading to 4.0.1, CentOS 6.3, KVM Hypervisor,  MySQL Server 5.1
>            Reporter: Nawawit Kessaraphong
>            Assignee: Alena Prokharchyk
>              Labels: database,, server,, upgrade
>             Fix For: 4.0.1
>
>
>  I had cloudstack 3.0.2 deployed since last year and just upgraded to 4.0.1. Using this repository  http://cloudstack.apt-get.eu/rhel/4.0/  and  following this guide  http://cloudstack.apache.org/docs/en-US/Apache_CloudStack/4.0.1-incubating/html/Release_Notes/upgrade-instructions.html#upgrade-from-3.0.2-to-4.0.1  which seems very good and descriptive.
> The upgrade process, however, had a problem. In step 9 where i try to start my management again. 
> The server didn't seems to start, i investigated the log  and found that database upgrade can not be performed
> """"""
> Database upgrade must be performed from 3.0.2.20120506223416 to 4.0.1.20130201075054
> The end upgrade version is actually at 4.0.0 but our management server code version is at 4.0.1.2013020107505
> """"""
> I can confirmed that i had installed version 4.0.1 of all cloud components (except cloud-baremetal where its doesn't work on CentOS 6) and the system once worked correctly on 3.0.2.
> Is there anything i can do to perform database upgrade to the new version.
> Best Regards
> Nawawit Kessaraphong
> part of /var/log/clod/management/managerment-server.log
> 2013-04-22 21:40:02,982 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) DB version = 3.0.2.20120506223416 Code Version = 4.0.1.20130201075054
> 2013-04-22 21:40:02,983 INFO  [cloud.upgrade.DatabaseUpgradeChecker] (main:null) Database upgrade must be performed from 3.0.2.20120506223416 to 4.0.1.20130201075054
> 2013-04-22 21:40:02,983 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.1.20130201075054
> 2013-04-22 21:40:02,985 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.1.20130201075054
>   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)
> ......
> ------------------------------------------

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