cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rayees Namathponnan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3759) [Automation] Attach volume on a vm deployed with startvm=False fails
Date Sat, 10 Aug 2013 00:12:48 GMT

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

Rayees Namathponnan commented on CLOUDSTACK-3759:
-------------------------------------------------

Observed below NPE

2013-07-13 16:46:57,813 DEBUG [cloud.api.ApiServlet] (catalina-exec-11:null) ===END===  10.223.240.194
-- GET  apiKey=-sI_ssiKDKw-kBxUNzCMCmLmKnoRzuRjUyWnFjY8EFCXZx-zqx9jwTYL9h3vOmgVmtuGSHvmJGfPC3Bv6Sm-9g&virtualmachineid=90ad53ea-1b8c-413b-b2ea-8acb6b640050&id=35f26aa3-9473-4c31-947f-a69a52a748e0&command=attachVolume&signature=ZEoADxUiwDn3R6PyVQ7p1QkoEQs%3D&response=json
2013-07-13 16:46:57,816 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) ===START===  10.223.240.194
-- GET  signature=jeb92on7VUtUo%2BEQYR%2BSiqupwAU%3D&apiKey=-sI_ssiKDKw-kBxUNzCMCmLmKnoRzuRjUyWnFjY8EFCXZx-zqx9jwTYL9h3vOmgVmtuGSHvmJGfPC3Bv6Sm-9g&command=queryAsyncJobResult&response=json&jobid=2f7a2e6c-1acd-4139-b597-8f6c13c9e541
2013-07-13 16:46:57,861 DEBUG [cloud.api.ApiServlet] (catalina-exec-4:null) ===END===  10.223.240.194
-- GET  signature=jeb92on7VUtUo%2BEQYR%2BSiqupwAU%3D&apiKey=-sI_ssiKDKw-kBxUNzCMCmLmKnoRzuRjUyWnFjY8EFCXZx-zqx9jwTYL9h3vOmgVmtuGSHvmJGfPC3Bv6Sm-9g&command=queryAsyncJobResult&response=json&jobid=2f7a2e6c-1acd-4139-b597-8f6c13c9e541
2013-07-13 16:46:57,869 DEBUG [storage.allocator.LocalStoragePoolAllocator] (Job-Executor-112:job-3074
= [ 2f7a2e6c-1acd-4139-b597-8f6c13c9e541 ]) LocalStoragePoolAllocator trying to find storage
pool to fit the vm
2013-07-13 16:46:57,885 ERROR [cloud.async.AsyncJobManagerImpl] (Job-Executor-112:job-3074
= [ 2f7a2e6c-1acd-4139-b597-8f6c13c9e541 ]) Unexpected exception while executing org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Caught: SELECT pool.id, SUM(IF(vol.state='Ready'
AND vol.account_id = ?, 1, 0)) FROM `cloud`.`storage_pool` pool LEFT JOIN `cloud`.`volumes`
vol ON pool.id = vol.pool_id WHERE pool.data_center_id = ?  AND pool.pod_id = ? AND pool.cluster_id
= ?  GROUP BY pool.id ORDER BY 2 ASC
        at com.cloud.storage.dao.VolumeDaoImpl.listPoolIdsByVolumeCount(VolumeDaoImpl.java:479)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reorderPoolsByNumberOfVolumes(AbstractStoragePoolAllocator.java:122)
        at org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.reOrder(AbstractStoragePoolAllocator.java:161)
        at org.apache.cloudstack.storage.allocator.AbstractStoragePoolAllocator.allocateToPool(AbstractStoragePoolAllocator.java:110)
        at com.cloud.storage.StorageManagerImpl.findStoragePool(StorageManagerImpl.java:428)
        at com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:672)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1538)
        at com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1840)
        at com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
        at org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd.execute(AttachVolumeCmd.java:122)
        at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:158)
        at com.cloud.async.AsyncJobManagerImpl$1.run(AsyncJobManagerImpl.java:531)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
        at java.util.concurrent.FutureTask.run(FutureTask.java:166)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
        at java.lang.Thread.run(Thread.java:679)
Caused by: java.lang.NullPointerException
        at com.cloud.storage.dao.VolumeDaoImpl.listPoolIdsByVolumeCount(VolumeDaoImpl.java:468)
        ... 31 more
2013-07-13 16:46:57,933 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-112:job-3074
= [ 2f7a2e6c-1acd-4139-b597-8f6c13c9e541 ]) Complete async job-3074 = [ 2f7a2e6c-1acd-4139-b597-8f6c13c9e541
], jobStatus: 2, resultCode: 530, result: Error Code: 530 Error text: Caught: SELECT pool.id,
SUM(IF(vol.state='Ready' AND vol.account_id = ?, 1, 0)) FROM `cloud`.`storage_pool` pool LEFT
JOIN `cloud`.`volumes` vol ON pool.id = vol.pool_id WHERE pool.data_center_id = ?  AND pool.pod_id
= ? AND pool.cluster_id = ?  GROUP BY pool.id ORDER BY 2 ASC

                
> [Automation] Attach volume on a vm deployed with startvm=False fails
> --------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3759
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3759
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation, Test
>    Affects Versions: 4.2.0
>            Reporter: Rayees Namathponnan
>            Assignee: Fang Wang
>            Priority: Blocker
>             Fix For: 4.2.0
>
>         Attachments: attachvolumefail.log
>
>
> Test cases failed from integration.component.test_stopped_vm.TestDeployVM
> Steps to reproduce 
> ------------------------------
> Step 1 : Create a VM from command line with start state is false
> Step 2 : Create a volume and attach the volume to stopped VM 
> Actual Result 
> Volume attachment failed; 
> Observed below error automation test log
>  
> attach volume failed!
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response for virtual
machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance: c90e1365-702a-4a68-86d6-f5d75437b623
> --------------------- >> end captured logging << ---------------------
> Stacktrace
>   File "/usr/local/lib/python2.7/unittest/case.py", line 318, in run
>     testMethod()
>   File "/Repo_30X/ipcl/cloudstack/test/integration/component/test_stopped_vm.py", line
611, in test_06_deploy_startvm_attach_detach
>     self.fail("Attach volume failed!")
>   File "/usr/local/lib/python2.7/unittest/case.py", line 393, in fail
>     raise self.failureException(msg)
> Attach volume failed!
> -------------------- >> begin captured logging << --------------------
> testclient.testcase.TestDeployVM: DEBUG: Deploying instance in the account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Deployed instance in account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Verify listVirtualMachines response for virtual
machine: c90e1365-702a-4a68-86d6-f5d75437b623
> testclient.testcase.TestDeployVM: DEBUG: Creating a volume in account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Created volume in account: test-S35RTQ
> testclient.testcase.TestDeployVM: DEBUG: Attaching volume to instance: c90e1365-702a-4a68-86d6-f5d75437b623
> --------------------- >> end captured logging << ---------------------

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