Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 11B3410A76 for ; Fri, 12 Jul 2013 18:09:49 +0000 (UTC) Received: (qmail 41054 invoked by uid 500); 12 Jul 2013 18:09:48 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 41038 invoked by uid 500); 12 Jul 2013 18:09:48 -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 40954 invoked by uid 500); 12 Jul 2013 18:09:48 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 40775 invoked by uid 99); 12 Jul 2013 18:09:48 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Jul 2013 18:09:48 +0000 Date: Fri, 12 Jul 2013 18:09:48 +0000 (UTC) From: "Brian Federle (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Reopened] (CLOUDSTACK-3226) UI - Scale vm errors are not shown on the UI MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-3226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Federle reopened CLOUDSTACK-3226: --------------------------------------- > UI - Scale vm errors are not shown on the UI > -------------------------------------------- > > Key: CLOUDSTACK-3226 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3226 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: UI > Affects Versions: 4.2.0 > Reporter: Nitin Mehta > Priority: Critical > Fix For: 4.2.0 > > > After calling the api there are calls like below ? Becuase of this the errors are no surfaced. Can we not take the job id returned > http://localhost:8080/client/api?command=queryAsyncJobResult&jobId=undefined&response=json&sessionkey=ZzJ%2Bboi4m%2Bg1ir2b13qfuNfMJXM%3D&_=1372318949678 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira