Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 20 Dec 2017 11:43:00 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13063994.1492146117000.502073.1513770180302@Atlassian.JIRA>
In-Reply-To: <JIRA.13063994.1492146117000@Atlassian.JIRA>
References: <JIRA.13063994.1492146117000@Atlassian.JIRA> <JIRA.13063994.1492146117361@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9875) Unable to re-apply Explicit
 dedication to VM
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 20 Dec 2017 11:43:06 -0000


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

ASF GitHub Bot commented on CLOUDSTACK-9875:
--------------------------------------------

rhtyd commented on issue #2042: CLOUDSTACK-9875: Unable to re-apply Explicit dedication to VM
URL: https://github.com/apache/cloudstack/pull/2042#issuecomment-353041712
 
 
   Tests LGTM, failures are not related to this PR. Merging.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


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