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 7F61E10393 for ; Mon, 10 Mar 2014 04:06:01 +0000 (UTC) Received: (qmail 96681 invoked by uid 500); 10 Mar 2014 04:06:00 -0000 Delivered-To: apmail-cloudstack-dev-archive@cloudstack.apache.org Received: (qmail 96582 invoked by uid 500); 10 Mar 2014 04:06:00 -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 96573 invoked by uid 99); 10 Mar 2014 04:05:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 04:05:59 +0000 X-ASF-Spam-Status: No, hits=-0.1 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy includes SPF record at spf.trusted-forwarder.org) Received: from [74.125.149.143] (HELO na3sys009aog130.obsmtp.com) (74.125.149.143) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Mar 2014 04:05:55 +0000 Received: from mail-we0-f179.google.com ([74.125.82.179]) (using TLSv1) by na3sys009aob130.postini.com ([74.125.148.12]) with SMTP ID DSNKUx06Dje9QVphOd98yDDdAy0iNfQoODcY@postini.com; Sun, 09 Mar 2014 21:05:34 PDT Received: by mail-we0-f179.google.com with SMTP id x48so7865531wes.38 for ; Sun, 09 Mar 2014 21:05:27 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=S0A3fERhj7ltPupQhCiKWX9hwVt5WW/4tpygy71git0=; b=FbS4SDZvS1cdWX2j/ARqcWNSGu1gf5bqvSpAwAlLQsnSDtqo37dKHdEs8tKyk2LkaE fBh/dnHoW0kOnzLyE67V5U8tBbjyn7B6RCQHECsyaLZdpxgz+eqlIrG5cRxffVKvaq+s jcF3ODDxq95DZlpEco4rQa9OSJA2zrrt9e2/9qMlzAAGz53lercdd7SiDRgexNPpKDbQ qmjzwntpio+qcASJnu23R0/hw6xmstFr1V0AVeeoZdYlvZ/ve+JhLfpteO3sqbyzjtBv nffREzu0MgAyGpO3dYQbRL5zkrXtK0ziEu4mfIyJFpBTLlRpesZ8SjQX7go19e26c6aV rdeQ== X-Gm-Message-State: ALoCoQmsjJ9ZQD/hV30Jzwun4ulWrtBnhsSgIYmaoRF8vl3thxKs+73/7ht90j2b+gTaYoBlyu2PZ7X5yovMeddZxz2qDM/0IsAqPm36oNY0wJqt64l3TInFvW0FmKS3NoK11CRyT9g0zDuKAI5e7V8eV1Y0hX87aZBV1926Cxll9W11DdoMYzM= X-Received: by 10.194.82.35 with SMTP id f3mr29452006wjy.36.1394424327293; Sun, 09 Mar 2014 21:05:27 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.194.82.35 with SMTP id f3mr29451999wjy.36.1394424327219; Sun, 09 Mar 2014 21:05:27 -0700 (PDT) Received: by 10.216.81.194 with HTTP; Sun, 9 Mar 2014 21:05:27 -0700 (PDT) In-Reply-To: References: Date: Mon, 10 Mar 2014 09:35:27 +0530 Message-ID: Subject: Re: CLOUDSTACK-5583: vmopsSnapshot plug-in (XenServer) does not return an error when it should From: Mandar Barve To: Mike Tutkowski Cc: cloudstack Content-Type: multipart/alternative; boundary=047d7bf0c106b0c5be04f438b654 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bf0c106b0c5be04f438b654 Content-Type: text/plain; charset=ISO-8859-1 Hi Mike, Did you get a chance to look at this? Thanks, Mandar On Wed, Mar 5, 2014 at 10:12 AM, Mandar Barve wrote: > I tested this with CS 4.3. > > Thanks, > Mandar > > > On Tue, Mar 4, 2014 at 9:09 PM, Mike Tutkowski < > mike.tutkowski@solidfire.com> wrote: > >> Hi, >> >> Can you tell me what release you tested this with? I noticed the problem >> while developing on CloudStack 4.3. >> >> Thanks! >> >> >> On Tue, Mar 4, 2014 at 3:43 AM, Mandar Barve wrote: >> >>> Hi, >>> I tried to reproduce the issue but couldn't get this to fail for >>> insufficient space. I then injected an exception trying to list files from >>> a non existent path (added this code in the "try" block). This landed me >>> into the exception handling code. It raised correct exception saying "file >>> not found" which was captured in the management server vmops log file. It >>> was not displayed by the GUI. GUI just reported Error (Are we looking for >>> GUI displaying error code?). The plugin code returns "0" immediately after >>> the line of code that raises exception but I think this applies only for >>> successful execution of the plugin code that reverts the snapshot. >>> >>> If any exception is raised (e.g. in the reported case here >>> insufficient space) then the code should return appropriate error message >>> to the caller as I found. In exception handling path return "0" wouldn't >>> execute. >>> >>> I don't see any problem here. Let me know if I am missing anything. >>> >>> Thanks, >>> Mandar >>> >> >> >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: mike.tutkowski@solidfire.com >> o: 303.746.7302 >> Advancing the way the world uses the cloud >> *(tm)* >> > > --047d7bf0c106b0c5be04f438b654--