Return-Path: X-Original-To: apmail-cloudstack-dev-archive@www.apache.org Delivered-To: apmail-cloudstack-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C26FBCB20 for ; Thu, 20 Nov 2014 11:40:53 +0000 (UTC) Received: (qmail 57658 invoked by uid 500); 20 Nov 2014 11:40:48 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 57610 invoked by uid 500); 20 Nov 2014 11:40:48 -0000 Mailing-List: contact dev-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 dev@cloudstack.apache.org Received: (qmail 57597 invoked by uid 99); 20 Nov 2014 11:40:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Nov 2014 11:40:47 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of daan.hoogland@gmail.com designates 209.85.213.173 as permitted sender) Received: from [209.85.213.173] (HELO mail-ig0-f173.google.com) (209.85.213.173) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Nov 2014 11:40:43 +0000 Received: by mail-ig0-f173.google.com with SMTP id r2so4598455igi.6 for ; Thu, 20 Nov 2014 03:40:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=Qji8ZonYY3uakKfyzpDCkgBeFUOMh9vriiBxPJdFRPc=; b=CAyxI+wAQcfcldBTGf42UD17AD9fqL3CI5yl5/XlCALNx0k1D1xBtCIk2VA82Zr68l l88jSxTfDrF7xx9c8Y31w+SLzN6GdU4UAv4pfdfKLfygio7oL4ssiuJeQVAKowiyDUlz 2Bqm4ZOLZEHbXlqVS5bxv6733z96I7WpRqR/sXrwDgmA8HH2t+HutsnF7T3yDh7Jq9u1 OEC5WIFICT2KBFVj/FZnPE9gULNeAsoftVigohKquoARoTfsdqmfripR/qriG6rZa28d VvZ8y55DS34p6CGf5N4SkcxheppBOGs3oduRr/2Mk/KIHU2NKvYs5JCrGKMObV44XBoS hETw== X-Received: by 10.50.43.197 with SMTP id y5mr8850957igl.33.1416483623098; Thu, 20 Nov 2014 03:40:23 -0800 (PST) MIME-Version: 1.0 Received: by 10.107.8.15 with HTTP; Thu, 20 Nov 2014 03:40:01 -0800 (PST) In-Reply-To: References: From: Daan Hoogland Date: Thu, 20 Nov 2014 12:40:01 +0100 Message-ID: Subject: Re: Advised to send to Dev list - Broken update from 4.4 to 4.4.1 To: dev Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org yes, it was pointed out to me that others ran into the issue and resolved it this way. The issue that during the 4.4.0 install something went wrong still stands:( On Thu, Nov 20, 2014 at 12:37 PM, Matthew Midgett wrote: > Yes but I hacked it so poorly that my networking was not right. So I roll= ed back. I'm guessing that if I add that field then it might upgrade? > > > Sent on a Sprint Samsung Galaxy S=C2=AE III > >
-------- Original message --------
From: Daan Hoogland
Date:11/20/2014 4:29 AM (GMT-05:00)
To: dev
Subject: Re: Advised= to send to Dev list - Broken update from 4.4 to 4.4.1
>
I did some more investigation > > In your sql dumps I found that the field was present in your 'editted' > version but not in either the 4.4.0 or the 4.4.1 versions. Did you get > this version of the db working? > > In the code I found that this statement should be executed in the > 430to440 upgrade step which should have been executed during the 4.4.0 > installation (the install does a 4.0.0 install and then upgrades up to > the version you are installing) That would mean that during the > initial install something went wrong. Did you see anything like this? > > thanks, > > > On Thu, Nov 20, 2014 at 9:44 AM, Daan Hoogland = wrote: >> I looked up the field that other people reported on the mailing list. >> >> ALTER TABLE `snapshot_policy` ADD `display` TINYINT( 1 ) NOT NULL DEFA= ULT '1' >> >> Can you try this in your upgraded system and restart? >> >> On Thu, Nov 20, 2014 at 3:47 AM, Matthew Midgett >> wrote: >>> 4.4.2-Snapshot fails at the same >>> Starting com.cloud.bridge.service.controller.s3.ServiceProvider_Enhance= rByCloudStack_8d3a94eb >>> >>> CONFIDENTIAL: This electronic mail, including any attachment(s) may con= tain information that is privileged, confidential, and/or otherwise protect= ed from disclosure to anyone other than its intended recipient(s). Any dis= semination or use of this electronic email or its contents (including any a= ttachments) by persons other than the intended recipient(s) is strictly pro= hibited. If you have received this message in error, please notify me imme= diately by reply email so that I may correct my internal records. Please t= hen delete the original message (including any attachments) in its entirety= . Thank you. >>> >>> -----Original Message----- >>> From: Daan Hoogland [mailto:daan.hoogland@gmail.com] >>> Sent: Wednesday, November 19, 2014 9:20 AM >>> To: dev >>> Subject: Re: Advised to send to Dev list - Broken update from 4.4 to 4.= 4.1 >>> >>> No, this would be for testing only! >>> >>> On Wed, Nov 19, 2014 at 2:45 PM, Matthew Midgett wrote: >>>> How do I go about doing this with centos 6.5 management servers and wi= ll there be a upgrade migration path back to 4.4.2 release? >>>> >>>> >>>> Sent on a Sprint Samsung Galaxy S=C2=AE III >>>> >>>>
-------- Original message --------
From: Daan Hoogland >>>>
Date:11/19/2014 4:54 AM >>>> (GMT-05:00)
To: dev
= Subject: Re: Advised to send to Dev list - Broken update from 4.4 to 4.4.1 =
Can you try upgrading to 4.4.2-SNAPSHOT (meaning the late= st state of the 4.4 branch)? to see if there is a difference there. >>>> >>>> On Tue, Nov 18, 2014 at 4:14 PM, Daan Hoogland wrote: >>>>> please sand them to daan hoogland on gmail if it needs to be private >>>>> >>>>> On Tue, Nov 18, 2014 at 4:10 PM, Matthew Midgett >>>>> wrote: >>>>>> It=E2=80=99s a few lines and Dan If you would like to view them I ca= n send them to you. The problem lies in the network part. >>>>>> >>>>>> CONFIDENTIAL: This electronic mail, including any attachment(s) may = contain information that is privileged, confidential, and/or otherwise prot= ected from disclosure to anyone other than its intended recipient(s). Any = dissemination or use of this electronic email or its contents (including an= y attachments) by persons other than the intended recipient(s) is strictly = prohibited. If you have received this message in error, please notify me i= mmediately by reply email so that I may correct my internal records. Pleas= e then delete the original message (including any attachments) in its entir= ety. Thank you. >>>>>> >>>>>> -----Original Message----- >>>>>> From: Daan Hoogland [mailto:daan.hoogland@gmail.com] >>>>>> Sent: Tuesday, November 18, 2014 9:20 AM >>>>>> To: dev >>>>>> Subject: Re: Advised to send to Dev list - Broken update from 4.4 to >>>>>> 4.4.1 >>>>>> >>>>>> Matthew, How big is the diff? >>>>>> >>>>>> On Tue, Nov 18, 2014 at 3:12 PM, Matthew Midgett wrote: >>>>>>> Thanks Nux I realized that after I posted but had to leave the offi= ce. >>>>>>> >>>>>>> As I side note I did the upgrade again yesterday and it failed at s= tarting the bridge networking. I dropped the DB and set it up like a fresh= install and that worked. I uploaded the upgraded db and it still failed to= start so I decided to diff them. I then ran win merge and merged a lot of= lines and it started again. My network was not showing correctly and that= made since, since it would fail at the part. I spent most of the day yeste= rday mucking around the db before I said screw it and rolled the upgrade ba= ck. I am 100% sure that the problem is in the db upgrade. What I really nee= d it is to give someone my pre update db and my post update db and let them= run compare the two. I am sure that a developer can help me. There was an= other user that was posting on my original email on the user list and his m= anagement server was failing at the same spot so it might not be related to= just me. >>>>>>> >>>>>>> My Db's of course contain sensitive information and I don't want to= just add a link for everyone to see. What is the best practice for this? >>>>>>> >>>>>>> >>>>>>> CONFIDENTIAL: This electronic mail, including any attachment(s) may= contain information that is privileged, confidential, and/or otherwise pro= tected from disclosure to anyone other than its intended recipient(s). Any= dissemination or use of this electronic email or its contents (including a= ny attachments) by persons other than the intended recipient(s) is strictly= prohibited. If you have received this message in error, please notify me = immediately by reply email so that I may correct my internal records. Plea= se then delete the original message (including any attachments) in its enti= rety. Thank you. >>>>>>> >>>>>>> -----Original Message----- >>>>>>> From: Matthew Midgett >>>>>>> [mailto:cloudstck@trick-solutions.com.INVALID] >>>>>>> Sent: Tuesday, November 18, 2014 6:49 AM >>>>>>> To: dev@cloudstack.apache.org >>>>>>> Subject: Advised to send to Dev list - Broken update from 4.4 to >>>>>>> 4.4.1 >>>>>>> >>>>>>> I tried again to update from 4.4.0 to 4.4.1 with centos management >>>>>>> server and xenserver 6.2. Here is the logs from the management >>>>>>> server and the catalina.out >>>>>>> >>>>>>> http://pastebin.com/mS0wjug7 >>>>>>> >>>>>>> http://pastebin.com/gwVCitvb >>>>>>> >>>>>>> I did fresh install with a single vm witg the db and management ser= ver on the same host just installed just fine. >>>>>>> >>>>>>> What should I do next ? >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Daan >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Daan >>>> >>>> >>>> >>>> -- >>>> Daan >>> >>> >>> >>> -- >>> Daan >>> >> >> >> >> -- >> Daan > > > > -- > Daan --=20 Daan