cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Koneti (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-3066) No Error message is popped up on UI when a dedicated resource is dedicated to another Account.
Date Wed, 19 Jun 2013 09:42:20 GMT


Kiran Koneti commented on CLOUDSTACK-3066:

The Same should be taken care for dedicating Zone/pod/cluster/host dedication through the
> No Error message is popped up on UI when a dedicated resource is dedicated to another
> ----------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-3066
>                 URL:
>             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
>             Fix For: 4.2.0
> 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
> Pod's Zone Z1 is already dedicated
>         at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicatePod(
>         at org.apache.cloudstack.api.commands.DedicatePodCmd.execute(
>         at
>         at$
>         at java.util.concurrent.Executors$
>         at java.util.concurrent.FutureTask$Sync.innerRun(
>         at
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message