Sangeetha Hariharan created CLOUDSTACK-2070:
-----------------------------------------------
Summary: Anti-Affinity - When Vm deployment fails because of not
being able to satisfy the anti-affinity rule , user should be provided with
more informative message.
Key: CLOUDSTACK-2070
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2070
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
Steps to reproduce the problem:
Anti-Affinity - When Vm deployment fails because of not being able to satisfy
the anti-affinity rule , user should be provided with more informative message.
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.
Error message that is returned to the user in this case is "Unable to create a
deployment for VM[User|test89011".
It would be better to provide the exact reason in this case , which would
provide input to the user to take corrective actions.
| 54 | 3 | 3 | NULL | NULL | NULL |
org.apache.cloudstack.api.command.user.vm.DeployVMCmd | NULL
|
{"sessionkey":"PIkvPPx4GBIe1DiXDE6DJ4ucJ2I\u003d","ctxUserId":"3","serviceOfferingId":"8b3e4dd8-f8ae-4e12-9551-604fbb6c6313","affinitygroupids":"d9136853-b785-4f3d-b975-9b3a9bf5d477","zoneId":"63fb31bd-de23-40d5-a710-4a6b922d153c","templateId":"aa7c5240-a625-11e2-8627-06d4460004b1","response":"json","id":"16","networkIds":"40ae3118-1004-4616-96ee-bd42beb9b8e1","hypervisor":"XenServer","name":"test89011","ctxAccountId":"3","ctxStartEventId":"215","displayname":"test89011"}
| 0 | 0 | NULL | 2 |
0 | 530 |
org.apache.cloudstack.api.response.ExceptionResponse/null/{"errorcode":533,"errortext":"Unable
to create a deployment for VM[User|test89011]"}
--
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
