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

ASF subversion and git services commented on CLOUDSTACK-2882:
-------------------------------------------------------------

Commit b39d302888f965c5c26812b556c2dc395c53bb5c in branch refs/heads/4.2 from 
[~tsp]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b39d302 ]

CLOUDSTACK-2882: Additional device types for IDE/SCSI

Signed-off-by: Prasanna Santhanam <t...@apache.org>

                
> [Automation] [KVM]Test case 
> "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due 
> to wrong mount point 
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2882
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2882
>             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: Rajesh Battala
>            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: 
> 10.208.10.22} {returns: ['mount: special device /dev/xvdd does not exist']}
> http://jenkins.cloudstack.org/view/cloudstack-qa/job/test-smoke-matrix/389/suite=test_vm_life_cycle/testReport/integration.smoke.test_vm_life_cycle/TestVMLifeCycle/test_10_attachAndDetach_iso/

--
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

Reply via email to