[jira] [Closed] (CLOUDSTACK-3052) Able to create a VM on the Dedicated Zone without using the affinity group.

["Kiran Koneti (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-3052?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kiran Koneti closed CLOUDSTACK-3052.
------------------------------------


Didn't see the issue in the latest build hence closing the issue
                
> Able to create a VM on the Dedicated Zone without using the affinity group.
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3052
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3052
>             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
>
>
> Followed the below steps :
> 1)Installed the CS and created multiple domains and accounts.
> 2)While creating a Zone in the initial steps dedicated the Zone to a particular account.
> 3)Once the zone is created and the system Vm's are up I logged in using the account which I have dedicated the Zone to.
> 4)Then tried to create a VM in the account without using the Affinity group,i tried it in two ways
>          a)Initially created a the Affinity group and didn't checkin the check box of affinity group while creating t  the VM then the VM creation was Successful.
>          b)Deleted the Affinity group and then tried to deploy the VM even then the VM creation is successful.
> Expected Result:
> The VM creation should be failed as the affinity group is not selected as there are no other shared hosts available for that account.
> My setup is as Follows:
> Single Zone-->Pod-->Cluster-->Host which is dedicated to the account.

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