You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/04/24 00:49:17 UTC

[jira] [Created] (CLOUDSTACK-2159) Anti-Affinity - When "HostAntiAffinityProcessor" plugin is not included in the deployment , deployVirtualMachine() command does not error out when passing the affiitygroupnames parameter.

Sangeetha Hariharan created CLOUDSTACK-2159:
-----------------------------------------------

             Summary: Anti-Affinity - When "HostAntiAffinityProcessor" plugin is not included in the deployment , deployVirtualMachine() command does not error out when passing the affiitygroupnames parameter.
                 Key: CLOUDSTACK-2159
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2159
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Management Server
    Affects Versions: 4.2.0
         Environment: Build from master
            Reporter: Sangeetha Hariharan
             Fix For: 4.2.0


Anti-Affinity - When "HostAntiAffinityProcessor" plugin is not included in the deployment , deployVirtualMachine() command does not error out when passing the affiitygroupnames parameter.

Steps to reproduce the problem:
I had few affinity groups created.
Then removed the "HostAntiAffinityProcessor" plugin from the management server and restarted the management server.

Tried to deploy a Vm in one of the existing affinity groups that already exists.

Affinity groups parameter is ignored and  Vm deployment succeeds.

In this case , there is no indication to the user that the Affinity groups parameter that he has used was actually not being respected.

Is it better in such cases for the API to error out indicating that HostAntiAffinityProcessor is not configured in the set up anymore.


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