[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687617#comment-13687617 ] Prasanna Santhanam commented on CLOUDSTACK-2882: I don't have a vmware environment handy, can you tell us the mount pattern for devices on vmware? > 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687726#comment-13687726 ] Sateesh Chodapuneedi commented on CLOUDSTACK-2882: -- >I don't have a vmware environment handy, can you tell us the mount pattern for >devices on vmware? Prasanna, I think you can use /dev/cdrom as mount point for iso device in case of VMware. > 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687762#comment-13687762 ] Prasanna Santhanam commented on CLOUDSTACK-2882: [~sateeshc] /dev/cdrom is for ISOs. I'm looking for the pattern for attached disks/volumes. On xen it goes like /dev/xvda,b,c and on KVM /dev/vda,b,c etc > 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13687893#comment-13687893 ] Sateesh Chodapuneedi commented on CLOUDSTACK-2882: -- >[~sateeshc] /dev/cdrom is for ISOs. I'm looking for the pattern for attached >disks/volumes. On xen it goes like /dev/xvda,b,c and on KVM /dev/vda,b,c etc VMware == For attached disks/volumes in VMware, For IDE disks - /dev/hdX, where X ranges from a-z For SCSI disks - /dev/sdX, where X ranges from a-z While deploying a VM in CloudStack, If the disk controller is SCSI (by default data disks are SCSI) the virtual disks goes on to take device name as /dev/sdX, where X ranges from a-z. Xen === BTW, disk naming convention in Xen is not /dev/xvda for all cases. Non-paravirtualized block devices use /dev/hdX for emulated IDE. Non-paravirtualized block devices use /dev/sdX for emulated SCSI. Paravirtualized block devices does use /dev/xvdX where X ranges from a-z. > 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688022#comment-13688022 ] Prasanna Santhanam commented on CLOUDSTACK-2882: Thanks Sateesh, that should be a complete enough listing for getting this test working. It looks like we have to do a hypervisor agnostic check of the disk attached in that case > 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13692508#comment-13692508 ] Rayees Namathponnan commented on CLOUDSTACK-2882: - Test cases failed in KVM Traceback (most recent call last): File "/Repo_30X/ipcl/cloudstack/test/integration/smoke/test_vm_life_cycle.py", line 755, in test_10_attachAndDetach_iso self.assert_(ssh_client.execute(cmds) == [], "mkdir failed within guest") File "/usr/local/lib/python2.7/site-packages/marvin/remoteSSHClient.py", line 66, in execute stdin, stdout, stderr = self.ssh.exec_command(command) File "/usr/local/lib/python2.7/site-packages/paramiko/client.py", line 374, in exec_command chan.exec_command(command) File "/usr/local/lib/python2.7/site-packages/paramiko/channel.py", line 215, in exec_command m.add_string(command) File "/usr/local/lib/python2.7/site-packages/paramiko/message.py", line 259, in add_string self.packet.write(s) TypeError: must be string or read-only character buffer, not list > 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point in KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677968#comment-13677968 ] ASF subversion and git services commented on CLOUDSTACK-2882: - Commit 195e823b10c5519f90aefa74a0cb104f0ff57b07 in branch refs/heads/master from [~tsp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=195e823 ] CLOUDSTACK-2882: Fix the diskdevice based on hypervisor KVM > /dev/vda Xen > /dev/xvdd 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: 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point in KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686461#comment-13686461 ] ASF subversion and git services commented on CLOUDSTACK-2882: - Commit 8801205fcf5c0fa8553e41d9730828134a16a7fd in branch refs/heads/master from [~tsp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;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 suite. 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: 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: 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: > 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
[jira] [Commented] (CLOUDSTACK-2882) Test case "test_vm_life_cycle.TestVMLifeCycle.test_10_attachAndDetach_iso" failing due to wrong mount point in KVM
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2882?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13686480#comment-13686480 ] ASF subversion and git services commented on CLOUDSTACK-2882: - Commit 8801205fcf5c0fa8553e41d9730828134a16a7fd in branch refs/heads/disk_io_throttling from [~tsp] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;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 suite. 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: 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: 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: > 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