You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Kiran Koneti (JIRA)" <ji...@apache.org> on 2013/06/19 11:42:20 UTC
[jira] [Commented] (CLOUDSTACK-3066) No Error message is popped up
on UI when a dedicated resource is dedicated to another Account.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-3066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687811#comment-13687811 ]
Kiran Koneti commented on CLOUDSTACK-3066:
------------------------------------------
The Same should be taken care for dedicating Zone/pod/cluster/host dedication through the UI.
> 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
> 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
> 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 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