cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Derrick Schneider (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (CLOUDSTACK-7846) deploydb fails when new version doesn't have any database upgrade
Date Wed, 05 Nov 2014 20:27:35 GMT

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

Derrick Schneider edited comment on CLOUDSTACK-7846 at 11/5/14 8:27 PM:
------------------------------------------------------------------------

Note that as a temporary workaround if you're running into this, you can return "4.4.2" in
Upgrade440to441.java

Current:

   public String getUpgradedVersion() {
        return "4.4.1";
    }


Works:
    public String getUpgradedVersion() {
        return "4.4.2";
    }




was (Author: derrickschneider):
Note that as a temporary workaround if you're running into this, you can return "4.4.2" in
Upgrade440to441.java

Current:
```    public String getUpgradedVersion() {
        return "4.4.1";
    }
```

Works:
```
    public String getUpgradedVersion() {
        return "4.4.2";
    }
```



> deploydb fails when new version doesn't have any database upgrade
> -----------------------------------------------------------------
>
>                 Key: CLOUDSTACK-7846
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7846
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.4.0
>         Environment: Mac OS X 10.8.3
>            Reporter: Derrick Schneider
>
> Having checked out branch 4.4, I followed along with the developer setup documentation
found here. http://docs.cloudstack.apache.org/en/master/developer_guide.html
> However, the deploydb failed with the error message: 
> ```
> Caused by: com.cloud.utils.exception.CloudRuntimeException: The end upgrade version is
actually at 4.4.1 but our management server code version is at 4.4.2-SNAPSHOT
> 	at com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:278)
> 	at com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:438)
> 	at com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:217)
> ```
> The relevant code is here:
> ```
>         if (Version.compare(trimmedCurrentVersion, upgrades[upgrades.length - 1].getUpgradedVersion())
!= 0) {
>             s_logger.error("The end upgrade version is actually at " + upgrades[upgrades.length
- 1].getUpgradedVersion() +
>                 " but our management server code version is at " + currentVersion);
>             throw new CloudRuntimeException("The end upgrade version is actually at "
+ upgrades[upgrades.length - 1].getUpgradedVersion() +
>                 " but our management server code version is at " + currentVersion);
>         }
> ```
> The problem seems to be that there's no Upgrade441to442 object with appropriate settings.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message