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 30147175D5 for ; Wed, 8 Oct 2014 18:45:35 +0000 (UTC) Received: (qmail 36101 invoked by uid 500); 8 Oct 2014 18:45:35 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 36072 invoked by uid 500); 8 Oct 2014 18:45:35 -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 36058 invoked by uid 500); 8 Oct 2014 18:45:35 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 36055 invoked by uid 99); 8 Oct 2014 18:45:34 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Oct 2014 18:45:34 +0000 Date: Wed, 8 Oct 2014 18:45:34 +0000 (UTC) From: "Jessica Wang (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CLOUDSTACK-3066) No Error message is popped up on UI when a dedicated resource is dedicated to another Account. 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-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jessica Wang updated CLOUDSTACK-3066: ------------------------------------- Attachment: 2014-10-08-jessica4B.PNG 2014-10-08-jessica4A.PNG 2014-10-08-jessica3B.PNG 2014-10-08-jessica3A.PNG 2014-10-08-jessica2B.PNG 2014-10-08-jessica2A.PNG 2014-10-08-jessica1B.PNG 2014-10-08-jessica1A.PNG > No Error message is popped up on UI when a dedicated resource is dedicated to another Account. > ---------------------------------------------------------------------------------------------- > > Key: CLOUDSTACK-3066 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3066 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Install and Setup > Affects Versions: 4.2.0 > Reporter: Kiran Koneti > Assignee: Jessica Wang > Fix For: 4.4.0 > > Attachments: 2014-10-08-jessica1A.PNG, 2014-10-08-jessica1B.PNG, 2014-10-08-jessica2A.PNG, 2014-10-08-jessica2B.PNG, 2014-10-08-jessica3A.PNG, 2014-10-08-jessica3B.PNG, 2014-10-08-jessica4A.PNG, 2014-10-08-jessica4B.PNG > > > Below are the steps followed. > 1)Dedicated a Zone to account1 from domain1 > 2)Then tried to dedicate the pod in that zone to another Account from different domain > 3)Then the UI Shows a message the POD is dedicated but there is a error message logged in the management server log as below: > 2013-06-19 20:24:07,842 ERROR [cloudstack.dedicated.DedicatedResourceManagerImpl] (Job-Executor-26:job-26) Cannot dedicate Pod. Its zone is already dedicated > 2013-06-19 20:24:07,847 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-26:job-26) Unexpected exception while executing org.apache.cloudstack.api.commands.DedicatePodCmd > com.cloud.utils.exception.CloudRuntimeException: Pod's Zone Z1 is already dedicated > at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicatePod(DedicatedResourceManagerImpl.java:266) > at org.apache.cloudstack.api.commands.DedicatePodCmd.execute(DedicatePodCmd.java:95) > at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:155) > at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:437) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) > at java.util.concurrent.FutureTask.run(FutureTask.java:166) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:679) > The expected result is the UI should also pop up a message saying the pod is dedicated to another Account instead of saying the dedication as successful. -- This message was sent by Atlassian JIRA (v6.3.4#6332)