cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "prashant kumar mishra (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3713) scaling up system vm is successful but UI popup message "Failed to scale vm"
Date Mon, 29 Jul 2013 10:55:49 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13722346#comment-13722346
] 

prashant kumar mishra commented on CLOUDSTACK-3713:
---------------------------------------------------

vm  Resource Allocation details on vecenter shows vm got update to new SO(attaching screenshot)

from DB it is clear ssvm got update to new SO

updating with API response and DB details
---------------------------------------------------------------
---------------------------------------------------------------
API 
1-requestI:http://10.147.*.253:8080/client/api?command=scaleVirtualMachine&id=e5802ad7-d3ef-4637-849d-a693184c5cc4&serviceofferingid=9f86bfbe-4d85-40b7-9c78-da64a09e2ed6&response=json&sessionkey=XlcwPCQhioo2g%2F9o5FHElJjlYSs%3D&_=1375093384139

response:{ "scalevirtualmachineresponse" : {"jobid":"7c358461-3081-4e33-8495-7f9f8a5a5fbf"}
}

2--request http://10.147.38.*:8080/client/api?command=queryAsyncJobResult&jobId=7c358461-3081-4e33-8495-7f9f8a5a5fbf&response=json&sessionkey=XlcwPCQhioo2g%2F9o5FHElJjlYSs%3D&_=1375093387920


response:{{ "queryasyncjobresultresponse" : {"accountid":"d5299774-f84a-11e2-90c7-0618b0000087","userid":"d52a97e6-f84a-11e2-90c7-0618b0000087","cmd":"org.apache.cloudstack.api.command.user.vm.ScaleVMCmd","jobstatus":0,"jobprocstatus":0,"jobresultcode":0,"created":"2013-07-29T21:17:38+0530","jobid":"7c358461-3081-4e33-8495-7f9f8a5a5fbf"}
}


3-request http://10.147.38.*:8080/client/api?command=queryAsyncJobResult&jobId=7c358461-3081-4e33-8495-7f9f8a5a5fbf&response=json&sessionkey=XlcwPCQhioo2g%2F9o5FHElJjlYSs%3D&_=1375093447992

response:{ "queryasyncjobresultresponse" : {"accountid":"d5299774-f84a-11e2-90c7-0618b0000087","userid":"d52a97e6-f84a-11e2-90c7-0618b0000087","cmd":"org.apache.cloudstack.api.command.user.vm.ScaleVMCmd","jobstatus":2,"jobprocstatus":0,"jobresultcode":530,"jobresulttype":"object","jobresult":{"errorcode":530,"errortext":"Failed
to scale vm"},"created":"2013-07-29T21:17:38+0530","jobid":"7c358461-3081-4e33-8495-7f9f8a5a5fbf"}
}


DB details
============
mysql> select * from vm_instance where id =1\G;
*************************** 1. row ***************************
                 id: 1
               name: s-1-VM
               uuid: e5802ad7-d3ef-4637-849d-a693184c5cc4
      instance_name: s-1-VM
              state: Running
     vm_template_id: 8
        guest_os_id: 15
private_mac_address: 06:89:92:00:00:04
 private_ip_address: 10.147.40.104
             pod_id: 1
     data_center_id: 1
            host_id: 1
       last_host_id: 1
           proxy_id: NULL
  proxy_assign_time: NULL
       vnc_password: AXRATdjJE86RIk8u4MaqYoMHM/m1HhjXtFBnF3mBYVw=
         ha_enabled: 0
      limit_cpu_use: 0
       update_count: 3
        update_time: 2013-07-29 14:10:46
            created: 2013-07-29 14:06:59
            removed: NULL
               type: SecondaryStorageVm
            vm_type: SecondaryStorageVm
         account_id: 1
          domain_id: 1
service_offering_id: 12
     reservation_id: 4e0e0c7b-3440-4a66-bf4a-68782351f22b
    hypervisor_type: VMware
   disk_offering_id: NULL
                cpu: NULL
                ram: NULL
              owner: NULL
              speed: NULL
          host_name: NULL
       display_name: NULL
      desired_state: NULL
         display_vm: 1
1 row in set (0.00 sec)

-->ssvm  SO  got updated to id=12 (was default SO )  after executing scalevmCMd


mysql> select * from service_offering where id=12\G ;
*************************** 1. row ***************************
                id: 12
               cpu: 1
             speed: 500
          ram_size: 2048
           nw_rate: NULL
           mc_rate: NULL
        ha_enabled: 0
     limit_cpu_use: 0
          host_tag: NULL
       default_use: 0
           vm_type: secondarystoragevm
          sort_key: 0
       is_volatile: 0
deployment_planner: NULL
1 row in set (0.00 sec)

ERROR:
No query specified

MS Log
=======
2013-07-29 21:17:38,128 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-16:job-16 =
[ 7c358461-3081-4e33-8495-7f9f8a5a5fbf ]) Executing org.apache.cloudstack.api.command.user.vm.ScaleVMCmd
for job-16 = [ 7c358461-3081-4e33-8495-7f9f8a5a5fbf ]

2013-07-29 21:18:40,995 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-16:job-16 =
[ 7c358461-3081-4e33-8495-7f9f8a5a5fbf ]) Complete async job-16 = [ 7c358461-3081-4e33-8495-7f9f8a5a5fbf
], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Failed to scale vm
















                
> 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: UI
>    Affects Versions: 4.2.0
>         Environment: hypervisor vmware esxi4.1
>            Reporter: prashant kumar mishra
>            Assignee: Jessica Wang
>             Fix For: 4.2.0
>
>         Attachments: Logs_DB.rar, screenshot-1.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

Mime
View raw message