[
https://issues.apache.org/jira/browse/CLOUDSTACK-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606123#comment-13606123
]
ASF subversion and git services commented on CLOUDSTACK-1720:
-------------------------------------------------------------
Commit beb15af0f267c59b7e070d279e1df960701b6cf6 in branch refs/heads/master
from [~bhaisaab]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-cloudstack.git;h=beb15af ]
CLOUDSTACK-1720: Add upgrade paths from 4.0.x to 4.2.0
Signed-off-by: Rohit Yadav <bhais...@apache.org>
> Have an upgrade path from 4.0.x to 4.1 and 4.0.x to 4.2.0
> ---------------------------------------------------------
>
> Key: CLOUDSTACK-1720
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1720
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Priority: Blocker
> Fix For: 4.1.0, 4.2.0
>
>
> I'd asked if this worked, but somehow this got missed while testing:
> We need to have an upgrade path from 4.0.x-incubating* to 4.0.1 and 4.0.x-*
> to 4.2
> [WARNING]
> java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:297)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: com.cloud.utils.exception.CloudRuntimeException: There is no
> upgrade path from 4.0.1-incubating to 4.2.0-SNAPSHOT
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.upgrade(DatabaseUpgradeChecker.java:194)
> at
> com.cloud.upgrade.DatabaseUpgradeChecker.check(DatabaseUpgradeChecker.java:357)
> at com.cloud.upgrade.DatabaseCreator.main(DatabaseCreator.java:209)
> ... 6 more
--
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
