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

ASF subversion and git services commented on CLOUDSTACK-10285:
--------------------------------------------------------------

Commit 3109c590e3d69de83a114ed6fdb12b706e46a7f3 in cloudstack's branch 
refs/heads/4.11 from [~rohithsharma]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=3109c59 ]

CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users (#2452)

4.10.0.0 users when upgrade to 4.11.0.0 may face db related
discrepancies due to some PRs that got merged without moving their sql
changes to 4.10->4.11 upgrade path. The 4.10.0.0 users can run those
missing sql statements manually and then upgrade to 4.11.0.0, since a
workaround like this is possible this ticket is not marked a blocker. In
4.11.1.0+, we'll move those changes from 4.9.3.0->4.10.0.0 upgrade path
to 4.10.0.0->4.11.0.0 upgrade path. Ideally we should not be doing this,
but this will fix issues for a future 4.10.0.0 user who may want to
upgrade to 4.11.1.0 or 4.12.0.0+.

Signed-off-by: Rohit Yadav <rohit.ya...@shapeblue.com>

> 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
> -------------------------------------------------------------
>
>                 Key: CLOUDSTACK-10285
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10285
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>            Priority: Critical
>             Fix For: 4.12.0.0, 4.11.1.0
>
>
> 4.10.0.0 users when upgrade to 4.11.0.0 may face db related discrepancies due 
> to some PRs that got merged without moving their sql changes to 4.10->4.11 
> upgrade path. The 4.10.0.0 users can run those missing sql statements 
> manually and then upgrade to 4.11.0.0, since a workaround like this is 
> possible this ticket is not marked a blocker. In 4.11.1.0+, we'll move those 
> changes from 4.9.3.0->4.10.0.0 upgrade path to 4.10.0.0->4.11.0.0 upgrade 
> path. Ideally we should not be doing this, but this will fix issues for a 
> future 4.10.0.0 user who may want to upgrade to 4.11.1.0 or 4.12.0.0+.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to