You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Joe Brockmeier (JIRA)" <ji...@apache.org> on 2013/04/05 20:53:16 UTC
[jira] [Resolved] (CLOUDSTACK-1747) mvn deploydb only creates 4.0
DB, not 4.1
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Brockmeier resolved CLOUDSTACK-1747.
----------------------------------------
Resolution: Fixed
I've added this to the "known issues" section. I think that's sufficient, but let me know if this should be emphasized elsewhere.
> mvn deploydb only creates 4.0 DB, not 4.1
> -----------------------------------------
>
> Key: CLOUDSTACK-1747
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1747
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Doc
> Affects Versions: 4.1.0
> Reporter: Min Chen
> Assignee: Joe Brockmeier
> Fix For: 4.1.0
>
>
> In 4.1 branch and on developer environment, if we run mvn -P developer -pl developer -Ddeploydb to deploy fresh db, it will create 4.1 CS DB, which will only run 4.0 CS schema. Only when we start MS, it will upgrade DB to 4.0, this is not designed behavior for 4.1 DB change. The correct behavior is that mvn deploydb should create a fresh 4.1 DB, then in next release we can move DB upgrade logic from MS start code. The commit for this is already in master, we just need to cherry-pick the following two commits from master to 4.1: 5b760f903f1a3145f62d05c1d3c142b710248026 and a32c6d5c9d50320b2526bc9e8a6820dd1e0987f0.
--
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