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/17 20:49:15 UTC

[jira] [Created] (CLOUDSTACK-2068) Anti-Affinity - When Vm deployment associated with anity-affinity group fails , it is still included in the vmlist of the anti-affiity group.

Sangeetha Hariharan created CLOUDSTACK-2068:
-----------------------------------------------

             Summary: Anti-Affinity - When Vm deployment associated with anity-affinity group fails , it is still included in the vmlist of the anti-affiity group. 
                 Key: CLOUDSTACK-2068
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2068
             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 associated with anity-affinity group fails , it is still included in the vmlist of the anti-affiity group.

Steps to reproduce the problem:
Have a deployment with 2 hosts.
As regular user - U1 , Create multiple anti-affinity group.
Deploy a 2 Vms  using anti-affinity group  say A1.

Deploy another Vm in the same anti-affinity group.

Vm deployment fails.

But this Vm that is in error state is included in the vm-list associated with the anti-affinity group.

http://10.223.131.202:8080/client/api?command=listAffinityGroups&response=json&sessionkey=85jEhgc7uzX7AIGDGjBf7e9sYmU%3D 

{ "listaffinitygroupsresponse" : { "count":1 ,"affinitygroup" : [  {"id":"d9136853-b785-4f3d-b975-9b3a9bf5d477","name":"sangee-1","description":"test-sangee-1","account":"sangee","domainid":"aa7821ac-a625-11e2-8627-06d4460004b1","domain":"ROOT","virtualmachineIds":["bc2d8100-cffa-4e51-bf30-c8ccc81509e3","16f94f97-9098-458b-9a2b-0f4cdb914e8e","59727cf1-cf4d-4a3f-9892-b1cb12b8648a"]} ] } }


+----+------------+---------+--------------------------------------+
| id | name       | state   | uuid                                 |
+----+------------+---------+--------------------------------------+
|  1 | s-1-VM     | Running | 3c766bab-44ae-45f4-9092-92fa7b20fefa |
|  2 | v-2-VM     | Running | 4dfa47bf-7ab6-4ffc-a996-b0d980a65922 |
|  3 | test123    | Stopped | 5cb3ac95-88c3-4343-800a-e27a69a379ec |
|  4 | r-4-VM     | Running | 9a95b4de-6279-41a3-9167-3ceec6b3d9af |
|  5 | hello-1    | Stopped | faf96d53-eeaa-4370-bea3-6d4fe8f577c7 |
|  6 | r-6-VM     | Running | 8eaaedba-e1cb-411e-b181-32bf5c494778 |
|  7 | yello      | Stopped | fe7c2231-030b-44ab-8a92-627fa3b9fb62 |
|  8 | sangee-123 | Stopped | 3dc9cc69-4874-4ce5-a520-9012720034b6 |
|  9 | newvm      | Stopped | d4d90437-2d13-4b22-a230-5cd5fde0b5c8 |
| 10 | again      | Stopped | c0c0ee3a-af91-4595-a1a3-4c3317489a03 |
| 11 | ubuntu     | Stopped | 36186bb2-9d1d-45fc-a569-88b94bc993a1 |
| 12 | test456    | Running | cb6e6fec-56dd-44ae-bf4f-dd29335ea24f |
| 13 | test890    | Running | 6ecf2715-1c64-43f2-abaf-b654d0f79b32 |
| 14 | test890    | Running | bc2d8100-cffa-4e51-bf30-c8ccc81509e3 |
| 15 | test8901   | Running | 16f94f97-9098-458b-9a2b-0f4cdb914e8e |
| 16 | test89011  | Error   | 59727cf1-cf4d-4a3f-9892-b1cb12b8648a |
+----+------------+---------+--------------------------------------+
16 rows in set (0.00 sec)

mysql> select * from affinity_group_vm_map ;
+----+-------------------+-------------+
| id | affinity_group_id | instance_id |
+----+-------------------+-------------+
|  1 |                 1 |          14 |
|  2 |                 1 |          15 |
|  3 |                 1 |          16 |
+----+-------------------+-------------+
3 rows in set (0.00 sec)



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