You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "prashant kumar mishra (JIRA)" <ji...@apache.org> on 2013/05/13 06:41:15 UTC
[jira] [Closed] (CLOUDSTACK-2146) system vm scaleup failed ;{
"scalevirtualmachineresponse" :
{"errorcode":530,"cserrorcode":9999,"errortext":"Failed to scale vm"} }
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
prashant kumar mishra closed CLOUDSTACK-2146.
---------------------------------------------
Tested on recent master code ;passed
> system vm scaleup failed ;{ "scalevirtualmachineresponse" : {"errorcode":530,"cserrorcode":9999,"errortext":"Failed to scale vm"} }
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2146
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2146
> 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: Hyp:Xenserver ;commit "2057221f4f1fd5afde422b367fc416d4e44275cb"
> Reporter: prashant kumar mishra
> Assignee: Harikrishna Patnala
> Priority: Critical
> Fix For: 4.2.0
>
> Attachments: access_log.2013-04-23.txt, apilog.log, catalina.out, management-server.log, screenshot-1.jpg, SMlog, xensource.log
>
>
> Tried to scaleup system vms ,it failed with API response "{ "scalevirtualmachineresponse" : {"errorcode":530,"cserrorcode":9999,"errortext":"Failed to scale vm"} }" and db got updated with new serivce offering .
> Steps to reproduce
> -----------------------------
> 1-Create a system offering for console pvm say s1(ram= 1GB,cpu=1GHZ)
> 2-Scale up vm using API
> Expected
> ---------------
> VM should get scaled up to new SO
> Actual
> ------------
> 1-Scaleup vm failed
> 2-New service offering got updated for console pvm in DB
> BD
> ----------
> mysql> select *from vm_instance where id=15\G;
> *************************** 1. row ***************************
> id: 15
> name: v-15-VM
> uuid: 0f8e8319-fdb3-4da1-b50c-aab2827d1c06
> instance_name: v-15-VM
> state: Running
> vm_template_id: 1
> guest_os_id: 133
> private_mac_address: 06:53:c8:00:00:03
> private_ip_address: 10.147.41.212
> pod_id: 1
> data_center_id: 1
> host_id: 5
> last_host_id: 5
> proxy_id: 15
> proxy_assign_time: 2013-04-23 11:37:51
> vnc_password: kEsfw5aA0VPlVqY3ohN7gWFN3Cr9BGFM41J+fcWpPTM=
> ha_enabled: 0
> limit_cpu_use: 0
> update_count: 7
> update_time: 2013-04-23 11:30:36
> created: 2013-04-23 11:24:07
> removed: NULL
> type: ConsoleProxy
> vm_type: ConsoleProxy
> account_id: 1
> domain_id: 1
> service_offering_id: 19
> reservation_id: d1cf507f-6a1f-4f3d-a380-59f57815a0b3
> hypervisor_type: XenServer
> disk_offering_id: NULL
> cpu: NULL
> ram: NULL
> owner: NULL
> speed: NULL
> host_name: NULL
> display_name: NULL
> desired_state: NULL
> 1 row in set (0.01 sec)
> mysql> select * from service_offering_view where id=19\G;
> *************************** 1. row ***************************
> id: 19
> uuid: b970c088-b4ba-4693-8a79-57ab84ad5c2b
> name: console
> display_text: console
> created: 2013-04-22 18:40:56
> tags: NULL
> removed: NULL
> use_local_storage: 0
> system_use: 1
> cpu: 1
> speed: 1000
> ram_size: 1024
> nw_rate: NULL
> mc_rate: NULL
> ha_enabled: 0
> limit_cpu_use: 0
> host_tag: NULL
> default_use: 0
> vm_type: consoleproxy
> sort_key: 0
> domain_id: NULL
> domain_uuid: NULL
> domain_name: NULL
> domain_path: NULL
> 1 row in set (0.00 sec)
> snippet of Management Server log
> --------------------------------------------------
> 2013-04-23 10:03:03,095 DEBUG [agent.transport.Request] (catalina-exec-24:null) Seq 5-264962068: Sending { Cmd , MgmtId: 7635042566263, via: 5, Ver: v1, Flags: 100111, [{"ScaleVmCommand":{"vm":{"id":1,"name":"v-15-VM","cpus":1,"speed":1000,"minRam":1024,"maxRam":1024,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"v-15-VM","cpus":1,"speed":1000,"minRam":1024,"maxRam":1024,"wait":0}}] }
> 2013-04-23 10:03:03,096 DEBUG [agent.transport.Request] (catalina-exec-24:null) Seq 5-264962068: Executing: { Cmd , MgmtId: 7635042566263, via: 5, Ver: v1, Flags: 100111, [{"ScaleVmCommand":{"vm":{"id":1,"name":"v-15-VM","cpus":1,"speed":1000,"minRam":1024,"maxRam":1024,"rebootOnCrash":false,"enableHA":false,"limitCpuUse":false},"vmName":"v-15-VM","cpus":1,"speed":1000,"minRam":1024,"maxRam":1024,"wait":0}}] }
> 2013-04-23 10:03:03,097 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-7:null) Seq 5-264962068: Executing request
> 2013-04-23 10:03:03,516 DEBUG [xen.resource.CitrixResourceBase] (DirectAgent-7:null) scaling VM v-15-VM is successful on host com.xensource.xenapi.Host@d9987304
> 2013-04-23 10:03:03,517 DEBUG [agent.manager.DirectAgentAttache] (DirectAgent-7:null) Seq 5-264962068: Response Received:
> 2013-04-23 10:03:03,518 DEBUG [agent.transport.Request] (DirectAgent-7:null) Seq 5-264962068: Processing: { Ans: , MgmtId: 7635042566263, via: 5, Ver: v1, Flags: 110, [{"ScaleVmAnswer":{"result":true,"details":"scaling VM v-15-VM is successful on host com.xensource.xenapi.Host@d9987304","wait":0}}] }
> 2013-04-23 10:03:03,518 DEBUG [agent.transport.Request] (catalina-exec-24:null) Seq 5-264962068: Received: { Ans: , MgmtId: 7635042566263, via: 5, Ver: v1, Flags: 110, { ScaleVmAnswer } }
> 2013-04-23 10:03:03,523 DEBUG [agent.manager.AgentAttache] (DirectAgent-7:null) Seq 5-264962068: No more commands found
> 2013-04-23 10:03:03,540 INFO [cloud.api.ApiServer] (catalina-exec-24:null) Failed to scale vm
> API logs
> -----------------
> 013-04-23 10:03:03,542 INFO [cloud.api.ApiServer] (catalina-exec-24:null) (userId=2 accountId=2 sessionId=6892F5D375A40DDD9AE71256C5D3BAAD) 10.146.0.13 -- GET command=scaleVirtualMachine&id=0f8e8319-fdb3-4da1-b50c-aab2827d1c06&serviceofferingid=b970c088-b4ba-4693-8a79-57ab84ad5c2b&response=json&sessionkey=uCt0bFRBfyC1h40Zd0EPReHtxOY%3D&_=1366706043136 530 Failed to scale 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