prashant kumar mishra created CLOUDSTACK-2148:
-------------------------------------------------

             Summary: Scale up  VM action button should  not be  visible/active 
 when vm is in stopped state 
                 Key: CLOUDSTACK-2148
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2148
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: API, UI
    Affects Versions: 4.2.0
            Reporter: prashant kumar mishra
            Priority: Minor
             Fix For: 4.2.0


Expected
--------------
1-->when vm is in stopped state we can change service offering (scale up and 
scale down) using change service offering action button ; so scaleup vm action 
button should not be visible  when vm is in stopped state

2->At api level it should be handled with some message saying that "you can't 
scaleup a vm in stopped state" 

Actual
----------
1-scaleup vm action button is in active state for vm in stopped state

2-API: when i tried to scaleup vm which is in stopped state using API ,i get 
response instead of failure message .but  service offering did not get changed 
in DB.

API
-----------
http://10.*.*.*:8080/client/api?command=scaleVirtualMachine&id=61316efe-8a7a-4a0d-8f8b-8286def57348&serviceofferingid=ef947658-9ecb-4701-8af3-6df8227dfb19&response=json&sessionkey=uCt0bFRBfyC1h40Zd0EPReHtxOY%3D&_=1366709720693
 


Response:
---------------
{ "scalevirtualmachineresponse" :  { "virtualmachine" : 
{"id":"61316efe-8a7a-4a0d-8f8b-8286def57348","name":"test","displayname":"test","account":"admin","domainid":"6c31cd9c-ab3b-11e2-b31f-06f1ac000077","domain":"ROOT","created":"2013-04-23T07:39:31-0400","state":"Stopped","haenable":false,"zoneid":"81cd8faa-17f0-45ca-9060-2c2180c07cf7","zonename":"zone","templateid":"6c3c96be-ab3b-11e2-b31f-06f1ac000077","templatename":"CentOS
 5.6(64-bit) no GUI (XenServer)","templatedisplaytext":"CentOS 5.6(64-bit) no 
GUI 
(XenServer)","passwordenabled":false,"serviceofferingid":"140a1907-d846-40ca-a15f-52e17713f5c9","serviceofferingname":"Small
 
Instance","cpunumber":1,"cpuspeed":500,"memory":512,"cpuused":"0%","networkkbsread":0,"networkkbswrite":0,"guestosid":"6c5dae8a-ab3b-11e2-b31f-06f1ac000077","rootdeviceid":0,"rootdevicetype":"ROOT","securitygroup":[],"nic":[{"id":"96ff0451-e622-4cbf-a979-76850124ef9e","networkid":"fcffc62e-e2b0-4840-a15a-142f065fff7e","networkname":"jia
 
ho","netmask":"255.255.255.0","gateway":"10.1.1.1","ipaddress":"10.1.1.198","traffictype":"Guest","type":"Isolated","isdefault":true,"macaddress":"02:00:73:e1:00:0c"}],"hypervisor":"XenServer","instancename":"i-2-17-VM","tags":[],"affinitygroup":[],"jobstatus":0}
 }  }

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

Reply via email to