cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3759) [Automation] Failed to attach volume to VM, while vm are in stopped state
Date Thu, 01 Aug 2013 16:21:49 GMT

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

Prasanna Santhanam commented on CLOUDSTACK-3759:
------------------------------------------------

[~Fang Wang] I think your test is incorrect when you've done it manually. You need to deploy
the VM in stopped state to start with. Not deploy it and stop it. If you do the former you
will see the test failure. Hope you were able to repro this before the fix.
                
> [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
> 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