cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0
Date Wed, 14 Feb 2018 10:55:00 GMT

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

ASF GitHub Bot commented on CLOUDSTACK-10285:
---------------------------------------------

rhtyd commented on issue #2452: CLOUDSTACK-10285: Fix db upgrade failure for 4.10.0.0 users
URL: https://github.com/apache/cloudstack/pull/2452#issuecomment-365567472
 
 
   Merged based on code reviews and test results.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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

Mime
View raw message