cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9875) Unable to re-apply Explicit dedication to VM
Date Tue, 19 Dec 2017 12:01:00 GMT


ASF GitHub Bot commented on CLOUDSTACK-9875:

blueorangutan commented on issue #2042: CLOUDSTACK-9875: Unable to re-apply Explicit dedication
to VM
   @rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run
smoke tests

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:

> Unable to re-apply Explicit dedication to VM
> --------------------------------------------
>                 Key: CLOUDSTACK-9875
>                 URL:
>             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:
> 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

View raw message