You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Yaron Rosenbaum (JIRA)" <ji...@apache.org> on 2015/02/21 11:39:11 UTC

[jira] [Created] (JCLOUDS-824) jClouds reports wrong volume names on ec2 / CoreOS

Yaron Rosenbaum created JCLOUDS-824:
---------------------------------------

             Summary: jClouds reports wrong volume names on ec2 / CoreOS
                 Key: JCLOUDS-824
                 URL: https://issues.apache.org/jira/browse/JCLOUDS-824
             Project: jclouds
          Issue Type: Bug
          Components: jclouds-compute
    Affects Versions: 1.8.1
         Environment: CoreOS on ec2, ami-d4bceabc
            Reporter: Yaron Rosenbaum



When using the above image, in a template (m1.medium, m1.small, etc), getHardware().getVolumes() ... getDevice()  returns strings similar to: /dev/sda2, but here is the device names it should return:

core@ip-10-0-0-153 ~ $ cat /proc/partitions 
major minor  #blocks  name

 202        0    8388608 xvda
 202        1     131072 xvda1
 202        2       2048 xvda2
 202        3    1048576 xvda3
 202        4    1048576 xvda4
 202        6     131072 xvda6
 202        7      65536 xvda7
 202        9    5959663 xvda9
 202       16  156352512 xvdb

I'm not sure if this is an issue with the ami or with some assumptions made in the jClouds code (for example, assuming that PV instances use the /sda# format whereas HVM return the /xvd# format)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)