[
https://issues.apache.org/jira/browse/CLOUDSTACK-3759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719148#comment-13719148
]
Fang Wang commented on CLOUDSTACK-3759:
---------------------------------------
Rayees,
I did a manually test:
1. create a new VM instance (fang-vm1) (on the zone 2 on your machine);
2. Create a new vol (fang-vol1);
3. wait for the VM come up, then stop the VM;
4. after the VM stop completes, I did a vol attach, and it works. no error
> [Automation] Failed to attach volume to VM, while vm are in stopped state
> --------------------------------------------------------------------------
>
> 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: CLOUDSTACK-3759.rar
>
>
> Test cases failed from integration.component.test_stopped_vm.TestDeployVM
> This issue is reproducible manually;
> Steps to reproduce
> ------------------------------
> Step 1 : Create a VM
> Step 2 : Stop VM
> Step 3 : Create a volume and attach the volume to stoped 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
