[
https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16361539#comment-16361539
]
ASF GitHub Bot commented on CLOUDSTACK-10285:
---------------------------------------------
blueorangutan 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-365082774
<b>Trillian test result (tid-2254)</b>
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 23691 seconds
Marvin logs:
https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr2452-t2254-kvm-centos7.zip
Intermitten failure detected: /marvin/tests/smoke/test_privategw_acl.py
Intermitten failure detected: /marvin/tests/smoke/test_hostha_kvm.py
Smoke tests completed. 65 look OK, 2 have error(s)
Only failed tests results shown below:
Test | Result | Time (s) | Test File
--- | --- | --- | ---
test_04_rvpc_privategw_static_routes | `Failure` | 277.99 |
test_privategw_acl.py
test_hostha_enable_ha_when_host_in_maintenance | `Error` | 3.43 |
test_hostha_kvm.py
----------------------------------------------------------------
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:
us...@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)
