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 => kilo-2

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

Title:
  EC2 'attaching' state is not reported for attaching volumes

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  When volume is attaching AWS reports 'attaching' in the volume attachment info:
  VOLUME	vol-b6baa9ff	 1		us-east-1b	in-use	2014-08-11T15:34:38.090Z
  ATTACHMENT	vol-b6baa9ff	i-afcc1f85	/dev/sdd	attaching	2014-08-11T15:41:24.000Z

  But Nova EC2 doesn't do it:
  VOLUME	vol-00000001	 1		nova	in-use	2014-08-10T19:51:06.000000
  ATTACHMENT	vol-00000001	None	None	None	None

  Also instance BDM has wrong volume state. AWS returns 'attaching':
    <deviceName>/dev/sdf</deviceName>
    <ebs>
        <volumeId>vol-f4524dbd</volumeId>
        <status>attaching</status>
        <attachTime>2014-08-12T20:24:13.000Z</attachTime>
        <deleteOnTermination>false</deleteOnTermination>
    </ebs>

  But Nova EC2 returns 'detached':
    <deviceName>/dev/vdf</deviceName>
    <ebs>
      <status>detached</status>
      <deleteOnTermination>false</deleteOnTermination>
      <volumeId>vol-00000001</volumeId>
      <attachTime/>
    </ebs>

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