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

Prachi Damle commented on CLOUDSTACK-4321:
------------------------------------------

This was an issue with the nonossComponentContext.xml being not changed to 
include the new AffinityGroupAccessChecker component.

This is already fixed in latest 4.2. Please re-test with a latest build.

Commit that fixed this issue is:

Author:         Prachi Damle ([email protected])
Author date:    24 hours ago (Tue Aug 13 11:11:52 2013 -0700)
Commit date:    24 hours ago (Tue Aug 13 11:12:27 2013 -0700)
Commit hash:    86fcd647ad9406463b9d9d0e9b2a88c745494c99

Changes:
- Include the new AffinityGroupAccessChecker in all *ComponentContext.xml.in

Contained in branches: 4.2
Contained in no tag
                
> Not able to deploy VM using the affinity groups.
> ------------------------------------------------
>
>                 Key: CLOUDSTACK-4321
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4321
>             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: Prachi Damle
>            Priority: Critical
>             Fix For: 4.2.0
>
>
> Created a setup in the below mentioned way: 
> Zone-->POD-->Cluster-->2Hosts. 
> 1)I created 2 domains apart from the Root Domain having two accounts for each 
> domain. 
> 2)Dedicated the Zone to non root domain. 
> 3)Dedicated the one host to account in the same domain. 
> 4)Observed that 2 affinity groups are created and the while deploying the VM 
> i have selected both the affinity groups and the VM creation Failed. 
> The expected Result is the VM creation should be successful as the Zone is 
> dedicated and both affinity groups are selected.
> The MS log shows the permission is granted to the account but the UI throws 
> an error message saying there is no way to detect the affinity group is 
> related to the account.
> THE MS log is as below:
> "2013-08-14 21:33:06,152 DEBUG [cloud.user.AccountManagerImpl] 
> (catalina-exec-20:null) Access granted to 
> Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] to Domain:2/Kiran/ by 
> DomainChecker_EnhancerByCloudStack_3d51253f
> 2013-08-14 21:33:06,155 DEBUG [cloud.user.AccountManagerImpl] 
> (catalina-exec-20:null) Access to 
> Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] granted to 
> Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] by 
> DomainChecker_EnhancerByCloudStack_3d51253f"
> The UI error message is as below:
> There's no way to confirm Acct[7d48a75d-4b99-4e89-8b17-a66a9aac3098-kiran1] 
> has access to AffinityGroup[78de168c-aa92-4e72-8902-ff3c77ae8be8]

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