From issues-return-89994-archive-asf-public=cust-asf.ponee.io@cloudstack.apache.org Wed Feb 14 11:55:05 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 77C4D180621 for ; Wed, 14 Feb 2018 11:55:04 +0100 (CET) Received: (qmail 38620 invoked by uid 500); 14 Feb 2018 10:55:03 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 38611 invoked by uid 500); 14 Feb 2018 10:55:03 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 38608 invoked by uid 99); 14 Feb 2018 10:55:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 14 Feb 2018 10:55:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 299E9C192B for ; Wed, 14 Feb 2018 10:55:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.011 X-Spam-Level: X-Spam-Status: No, score=-109.011 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, KAM_NUMSUBJECT=0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id McPjoPbjr5oe for ; Wed, 14 Feb 2018 10:55:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 46AD95F477 for ; Wed, 14 Feb 2018 10:55:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BEF6FE00A6 for ; Wed, 14 Feb 2018 10:55:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 7576F240F6 for ; Wed, 14 Feb 2018 10:55:00 +0000 (UTC) Date: Wed, 14 Feb 2018 10:55:00 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-10285) 4.10.0.0 users face upgrade issues when upgrading to 4.11.0.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-10285?page=3Dcom.atl= assian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId= =3D16363786#comment-16363786 ]=20 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=3Dcloudstack.git;h=3D3109c59 ] 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 > 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-102= 85 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the defa= ult.)=20 > 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=C2=A0related discrepa= ncies due to some PRs that got merged without moving their sql=C2=A0changes= to 4.10->4.11 upgrade path. The 4.10.0.0 users can run those missing sql= =C2=A0statements 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.1= 1.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)