| 2014-08-11 16:22:54 |
Feodor Tersin |
bug |
|
|
added bug |
| 2014-08-11 16:29:22 |
Feodor Tersin |
nova: assignee |
|
Feodor Tersin (ftersin) |
|
| 2014-08-13 05:03:14 |
Feodor Tersin |
description |
When volume is attaching AWS reports 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 |
When volume is attaching AWS reports 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> |
|
| 2014-08-13 05:14:25 |
Feodor Tersin |
summary |
EC2 attachment set is absent for attaching/detaching volumes |
EC2 'attaching' state is not reported for attaching volumes |
|
| 2014-08-13 05:15:30 |
Feodor Tersin |
description |
When volume is attaching AWS reports 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> |
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> |
|
| 2014-08-13 06:36:41 |
OpenStack Infra |
nova: status |
New |
In Progress |
|
| 2014-08-25 15:18:13 |
Sahid Orentino |
nova: importance |
Undecided |
Wishlist |
|
| 2014-09-17 21:31:04 |
Sean Dague |
tags |
|
ec2 |
|
| 2015-01-15 13:40:34 |
OpenStack Infra |
nova: status |
In Progress |
Fix Committed |
|
| 2015-02-05 20:22:37 |
Thierry Carrez |
nova: status |
Fix Committed |
Fix Released |
|
| 2015-02-05 20:22:37 |
Thierry Carrez |
nova: milestone |
|
kilo-2 |
|
| 2015-04-30 09:19:32 |
Thierry Carrez |
nova: milestone |
kilo-2 |
2015.1.0 |
|
