[jira] [Created] (CLOUDSTACK-2155) Anti-Affinity -When Vm deployment is done in parallel , anti-affinity rule is not honored.

["Sangeetha Hariharan (JIRA)" <ji...@apache.org>]

Sangeetha Hariharan created CLOUDSTACK-2155:
-----------------------------------------------

             Summary: Anti-Affinity -When Vm deployment is done in parallel , anti-affinity rule is not honored.
                 Key: CLOUDSTACK-2155
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2155
             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
            Priority: Critical
             Fix For: 4.2.0


Anti-Affinity - When Vm deployment is done in parallel , anti-affinity rule is not honored.

Steps to reproduce the problem:

Setup:
Advanced zone with 6 hosts.

Create a new anti-affnity rule.

Deploy 5 Vms in this anti-affnity rule.

We see that some of the vms that belong to the same anti-affinity rules are getting deployed on the same host.

select * from affinity_group_vm_map;
| 60 |                22 |          63 |
| 61 |                22 |          65 |
| 62 |                22 |          64 |
| 63 |                22 |          66 |
| 64 |                22 |          67 |
| 65 |                22 |          68 |
+----+-------------------+-------------+
30 rows in set (0.00 sec)

mysql> select host_id,id,state from vm_instance where id > 60;
+---------+----+-----------+
| host_id | id | state     |
+---------+----+-----------+
|    NULL | 61 | Expunging |
|       6 | 62 | Running   |
|       9 | 63 | Running   |
|       8 | 64 | Running   |
|       8 | 65 | Running   |
|       8 | 66 | Running   |
|       7 | 67 | Running   |
|       7 | 68 | Running   |
+---------+----+-----------+
8 rows in set (0.00 sec)

Will attach management-server log.


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