yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-1

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1165973

Title:
  wrong instance bdm response in ec2 api

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) grizzly series:
  Fix Committed

Bug description:
  when describing an instance with an attached volume, it will get the
  following response:

  <DescribeInstancesResponse xmlns="http://ec2.amazonaws.com/doc/2010-08-31/";>
    <requestId>req-4ddb9332-7068-4b7d-8d82-8f64d49e8e11</requestId>
    <reservationSet>
      <item>
        <ownerId>7dd8607e7d294efc845ccf68f8d282b7</ownerId>
        <groupSet>
          <item>
            <groupId>default</groupId>
          </item>
        </groupSet>
        <reservationId>r-z0xn0h0g</reservationId>
        <instancesSet>
          <item>
            <blockDeviceMapping>
              <item>
                <deviceName>/dev/vdd</deviceName>
                <ebs>
                  <status>in-use</status>
                  <deleteOnTermination>false</deleteOnTermination>
                  <volumeId>1a9ca4f2-0151-45c3-b0e7-196615bc6773</volumeId>
                  <attachTime></attachTime>
                </ebs>
              </item>
            </blockDeviceMapping>
            <placement>
              <availabilityZone>nova</availabilityZone>
            </placement>
            <keyName/>
            <instanceId>i-00001882</instanceId>
            <instanceState>
              <code>16</code>
              <name>running</name>
            </instanceState>
            <publicDnsName/>
            <imageId>ami-00000133</imageId>
            <productCodesSet/>
            <privateDnsName>server-0aa61ca2-ab25-4318-a406-8b96bc588557</privateDnsName>
            <dnsName>server-0aa61ca2-ab25-4318-a406-8b96bc588557</dnsName>
            <launchTime>2013-03-29T07:15:19.000Z</launchTime>
            <amiLaunchIndex>0</amiLaunchIndex>
            <rootDeviceName>/dev/vda</rootDeviceName>
            <rootDeviceType>instance-store</rootDeviceType>
            <ipAddress>10.0.0.3</ipAddress>
            <instanceType>m1.small</instanceType>
            <privateIpAddress>10.0.0.3</privateIpAddress>
          </item>
        </instancesSet>
      </item>
    </reservationSet>
  </DescribeInstancesResponse>

  
  in the blockDeviceMapping, the volumeId should use ec2 id instead of uuid and the status should be 'attached' rather than 'in-use'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1165973/+subscriptions