cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point in KVM
Date Tue, 18 Jun 2013 07:19:20 GMT


ASF subversion and git services commented on CLOUDSTACK-2882:

Commit 8801205fcf5c0fa8553e41d9730828134a16a7fd in branch refs/heads/master from [~tsp]
[;h=8801205 ]

CLOUDSTACK-2882: Correct the secondary disk device on KVM

On kvm the disk device serial order is /dev/vda|vdb|vdc and so on.
This also fixes CLOUDSTACK-3018 and removes the redundant test in
blocker bugs. The snapshot related tests are now include in snapshots

Signed-off-by: Prasanna Santhanam <>

> Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due
to wrong mount point in KVM
> ------------------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2882
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Automation
>    Affects Versions: 4.2.0
>         Environment: Automation - BVT 
>            Reporter: Rayees Namathponnan
>            Assignee: Prasanna Santhanam
>             Fix For: 4.2.0
> Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due
to wrong mount point in KVM
> Test case failing with below error
> paramiko.transport: INFO: Secsh channel 3 opened.
> paramiko.transport: DEBUG: [chan 3] Sesch channel 3 request ok
> sshClient: DEBUG: {Cmd: mount -rt iso9660 /dev/xvdd /mnt/tmp via Host:}
{returns: ['mount: special device /dev/xvdd does not exist']}

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:

View raw message