[
https://issues.apache.org/jira/browse/CLOUDSTACK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prasanna Santhanam reopened CLOUDSTACK-3759:
--------------------------------------------
Still occurs against a devcloud2 environment when running the stopped VM test
~/workspace/cloudstack/incubator-cloudstack(branch:4.2*) ยป nosetests
--with-marvin --marvin-config=setup/dev/advanced.cfg
test/integration/component/test_stopped_vm.py --load -a tags=needle
Test Deploy Virtual Machine with startVM=false and attach volume ... FAIL
======================================================================
FAIL: Test Deploy Virtual Machine with startVM=false and attach volume
----------------------------------------------------------------------
Traceback (most recent call last):
File
"/Users/tsp/workspace/cloudstack/incubator-cloudstack/test/integration/component/test_stopped_vm.py",
line 430, in test_04_deploy_startvm_false_attach_volume
self.fail("Attach volume failed!")
AssertionError: Attach volume failed!
-------------------- >> begin captured logging << --------------------
test_04_deploy_startvm_false_attach_volume
(integration.component.test_stopped_vm.TestDeployVM): DEBUG: Deploying instance
in the account:
test-TestVMAccountLimit-test_04_deploy_startvm_false_attach_volume-UBG4OT
test_04_deploy_startvm_false_attach_volume
(integration.component.test_stopped_vm.TestDeployVM): DEBUG: Deployed instance
in account:
test-TestVMAccountLimit-test_04_deploy_startvm_false_attach_volume-UBG4OT
test_04_deploy_startvm_false_attach_volume
(integration.component.test_stopped_vm.TestDeployVM): DEBUG: Verify
listVirtualMachines response for virtual machine:
f153b441-9597-4dd9-aa34-93e56182dafa
test_04_deploy_startvm_false_attach_volume
(integration.component.test_stopped_vm.TestDeployVM): DEBUG: Creating a volume
in account:
test-TestVMAccountLimit-test_04_deploy_startvm_false_attach_volume-UBG4OT
test_04_deploy_startvm_false_attach_volume
(integration.component.test_stopped_vm.TestDeployVM): DEBUG: Created volume in
account:
test-TestVMAccountLimit-test_04_deploy_startvm_false_attach_volume-UBG4OT
test_04_deploy_startvm_false_attach_volume
(integration.component.test_stopped_vm.TestDeployVM): DEBUG: Attaching volume
to instance: f153b441-9597-4dd9-aa34-93e56182dafa
--------------------- >> end captured logging << ---------------------
----------------------------------------------------------------------
Ran 1 test in 21.357s
FAILED (failures=1)
---------------------------------------------
Management server reports:
2013-08-06 12:39:29,079 ERROR [cloud.async.AsyncJobManagerImpl]
(Job-Executor-3:job-10 = [ 43fa0ea0-ee88-4b41-ad87-7ddc167ed314 ]) Unexpected
exception while executing
org.apache.cloudstack.api.command.user.volume.AttachVolumeCmd
com.cloud.utils.exception.CloudRuntimeException: Unable to find storage pool
when create volumeDataDisk
at
com.cloud.storage.VolumeManagerImpl.createVolume(VolumeManagerImpl.java:677)
at
com.cloud.utils.component.ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept(ComponentInstantiationPostProcessor.java:125)
at
com.cloud.storage.VolumeManagerImpl.createVolumeOnPrimaryStorage(VolumeManagerImpl.java:1527)
at
com.cloud.storage.VolumeManagerImpl.attachVolumeToVM(VolumeManagerImpl.java:1829)
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:439)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:680)
Latest management server logs are attached
> [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
> Environment: KVM
> Automation
> 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
