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/12 13:18:20 UTC

[jira] [Comment Edited] (CLOUDSTACK-2948) Vm is created using the root directory on the Zone which is dedicated to a Sub domain.

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-2948?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681124#comment-13681124 ] 

Kiran Koneti edited comment on CLOUDSTACK-2948 at 6/12/13 11:18 AM:
--------------------------------------------------------------------

After this I released the dedicated zone from the subdomain 1 and tried to dedicate it to the subdomain 2 then observed the below error message:

2013-06-12 22:04:59,701 INFO  [cloudstack.dedicated.DedicatedResourceManagerImpl] (Job-Executor-35:job-49) Host 1 found to be unsuitable for explicit dedication as it is running instances of another domain
2013-06-12 22:04:59,703 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-35:job-49) Unexpected exception while executing org.apache.cloudstack.api.commands.DedicateZoneCmd
com.cloud.utils.exception.CloudRuntimeException: Host 1 found to be unsuitable for explicit dedication as it is running instances of another domain
        at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:575)
        at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostsSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:586)
        at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicateZone(DedicatedResourceManagerImpl.java:211)
        at org.apache.cloudstack.api.commands.DedicateZoneCmd.execute(DedicateZoneCmd.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)
2013-06-12 22:04:59,704 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-35:job-49) Complete async job-49, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Host 1 found to be unsuitable for explicit dedication as it is running instances of another domain

Then I tried to dedicate it back to the same subdomain1 then also I observed the same error message ,and when it tried to dedicate it to the Root domain there are no exceptions seen.
                
      was (Author: kiran_koneti):
    After this I released the dedicated zone from the subdomain 1 and tried to dedicate it to the subdomain 2 then observed the below error message:

2013-06-12 22:04:59,701 INFO  [cloudstack.dedicated.DedicatedResourceManagerImpl] (Job-Executor-35:job-49) Host 1 found to be unsuitable for explicit dedication as it is running instances of another domain
2013-06-12 22:04:59,703 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-35:job-49) Unexpected exception while executing org.apache.cloudstack.api.commands.DedicateZoneCmd
com.cloud.utils.exception.CloudRuntimeException: Host 1 found to be unsuitable for explicit dedication as it is running instances of another domain
        at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:575)
        at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.checkHostsSuitabilityForExplicitDedication(DedicatedResourceManagerImpl.java:586)
        at org.apache.cloudstack.dedicated.DedicatedResourceManagerImpl.dedicateZone(DedicatedResourceManagerImpl.java:211)
        at org.apache.cloudstack.api.commands.DedicateZoneCmd.execute(DedicateZoneCmd.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)
2013-06-12 22:04:59,704 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-35:job-49) Complete async job-49, jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Host 1 found to be unsuitable for explicit dedication as it is running instances of another domain

And when it tried to dedicate it to the Root domain there are no exceptions seen.
                  
> Vm is created using the root directory on the Zone which is dedicated to a Sub domain.
> --------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2948
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2948
>             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: Saksham Srivastava
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Below are the steps followed:
> 1)In a freshly installed host created a Sub domain under the root Domain.(domain kiran is created).
> 2)While creating a Zone dedicated it to the subdomain created in the step1.
> 3)The Zone creation was Successful .
> 4)Then logged in as the root user and tried to create a VM in the Zone which is dedicated to the Subdomain.
> 5)The VM creation was successful.
> Expected Result is the VM creation from the root domain should fail in this Zone as the Zone is dedicated to another Subdomain.

--
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