cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9875) Unable to re-apply Explicit dedication to VM
Date Wed, 20 Dec 2017 11:43:00 GMT

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

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

Commit cd637fd05f7c893824319c3040288166c82d6371 in cloudstack's branch refs/heads/master from
[~harikrishna.patnala]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=cd637fd ]

CLOUDSTACK-9875: Unable to re-apply Explicit dedication to VM (#2042)

Problem:
When a VM is deployed with in an Affinity group which has the cluster dedicated to a subdomain
(zone is dedicated to parent domain) it is getting successful. We can also stop the vm and
remove the affinity group, but if you want to add back the affinity it is failing.

Root cause:
During VM deployment there is clear check on affinity type (account/domain). Here since the
acl_type is "domain" it does not expect to be same owner for entities.
But during update of affinity to VM there is no specific check for acl_type "domain".

Solution:
Fix is to make the access check similar to VM deployment where it does not expect to be same
owner for entities if the acl_type is "domain".

> Unable to re-apply Explicit dedication to VM
> --------------------------------------------
>
>                 Key: CLOUDSTACK-9875
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9875
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Harikrishna Patnala
>            Assignee: Harikrishna Patnala
>             Fix For: 4.11.0.0
>
>
> When a VM is deployed with in an Affinity group which has the cluster dedicated to a
subdomain (zone is dedicated to parent domain) it is getting successful. We can also stop
the vm and remove the affinity group, but if you want to add back the affinity it is failing.
> Following are the steps to reproduce
> 1. I had created a Domain (Glass SA Parent Domain) and under it a subdomain (Glass SA
Subdomain) and created an account to it.
> 2. Apply dedication to the zone for primary domain (Glass SA Parent Domain)
> 3. Apply dedication to the cluster for sub domain (Glass SA Subdomain)
> 4. Logged in with the Account of Subdomain.
> 5. Created an instance with the affinity (DedicatedGrp-domain-Glass SA Subdomain) - the
dedication set with the cluster for the subdomain.
> 6. Powered off the VM, removed the affinity.
> 7. Tried adding back (the cluster affinity subdomain) - gives the error "Entity affinity
Group () and entity Acct () belong to different accounts" 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message