[
https://issues.apache.org/jira/browse/CLOUDSTACK-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13727630#comment-13727630
]
prashant kumar mishra commented on CLOUDSTACK-3713:
---------------------------------------------------
Jessica,
same changes are required for xen also
currently scaleVirtualMachine is getting called for system vms on xen
http://10.147.38.237:8080/client/api?command=scaleVirtualMachine&id=767150c9-f20b-44cd-a279-05dc17135975&serviceofferingid=a48b5a35-bede-4ae7-9847-62f2a7c1f8f5&response=json&sessionkey=78Bl8pTcDYWjSIRe3GhLidV%2BmyA%3D&_=1375446631913
> scaling up system vm is successful but UI popup message "Failed to scale vm"
> ------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3713
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3713
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: API
> Affects Versions: 4.2.0
> Environment: hypervisor vmware esxi4.1
> Reporter: prashant kumar mishra
> Assignee: Jessica Wang
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: Logs_DB.rar, New_logs_db.rar, screenshot-1.jpg,
> vmware_Resource_allocation .jpg
>
>
> Steps to reproduce
> -----------------------------
> 1-Prepare a CS setup with vmware esxi5.1
> 2-create system offering for ssvm and cpvm
> 3-Try to scale up ssvm /cpvm
> Actual
> -------------
> scaling up was successful but UI popup message "Failed to scale up vm"
--
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
