[jira] [Created] (CLOUDSTACK-7846) deploydb fails when new version doesn't have any database upgrade

["Derrick Schneider (JIRA)" <ji...@apache.org>]

Derrick Schneider created CLOUDSTACK-7846:
---------------------------------------------

             Summary: 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)