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

ASF subversion and git services commented on CLOUDSTACK-2948:
-------------------------------------------------------------

Commit 201c0651ccec02f16e3ca45058bbe00f4dfdaae0 in branch refs/heads/master 
from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=201c065 ]

CLOUDSTACK-2948, Explicit dedication processor wasn't added to nonoss 
components context xml. The processor was never picked up to evaluate which 
hosts to avoid during deployment. Adding the explicit processor to the list of 
available processors.

                
> 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: Devdeep Singh
>            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 and created affinity group 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

Reply via email to