cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanna Santhanam (JIRA)" <>
Subject [jira] [Assigned] (CLOUDSTACK-2882) [Automation] [VmWare]Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point
Date Fri, 02 Aug 2013 10:29:50 GMT


Prasanna Santhanam reassigned CLOUDSTACK-2882:

    Assignee: Rayees Namathponnan  (was: Prasanna Santhanam)

Unable to reproduce this with standard guests (CentOS 5.5, CentOS 6.4) on a vmware cluster.
Can you attach ISO on a vmware VM and tell me the device name on your guest? I see Sateesh
mentioned all vmware guests should follow /dev/cdrom as the conventional place for ISOs, but
that is already included in the test. It seems this is still failing.

Having that information will be helpful to correct the test for vmware
> [Automation] [VmWare]Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso"
failing due to wrong mount point 
> ---------------------------------------------------------------------------------------------------------------------------------
>                 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: Rayees Namathponnan
>            Priority: Blocker
>             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