search

termie / nova-migration-demo

Nova is a cloud computing fabric controller (the main part of an IaaS system). It is written in Python.
http://openstack.org/projects/compute/
Apache License 2.0
2 stars 0 forks source link

Attach volume sometimes incorrectly reports success #176

Open termie opened 13 years ago

termie commented 13 years ago

Recently while I was refactoring the smoke tests, I found that attach volume is reporting success even when the operation fails. I was able to work around this in the smoke tests by waiting longer before attaching. My initial sense is that the volume is reporting its state as "available" some small amount of time (5-15 seconds?) before it is really available.

Here is a snippet from the volume smoke tests that show how I was forced to work around the issue:

http://paste.openstack.org/show/100/

Imported from Launchpad using lp2gh.

termie commented 13 years ago

(by soren) The volume driver's create_export method should block until the device is actually ready. There must be some way to check when vblade (assuming the you're using AoE) has actually gotten its act together and exported the device?

termie commented 13 years ago

(by vishvananda) This is apparently happening with iscsi. I'd love to get some tracebacks because I'm not sure what exactly is going to quickly. I guess it is possible that the iscsi target shell is returning before the target is actually created, but this seems unlikely.

Vish

On Nov 22, 2010, at 1:36 AM, Soren Hansen wrote:

The volume driver's create_export method should block until the device is actually ready. There must be some way to check when vblade (assuming the you're using AoE) has actually gotten its act together and exported the device?

Attach volume sometimes incorrectly reports success https://bugs.launchpad.net/bugs/673756 You received this bug notification because you are a member of Nova Bugs, which is subscribed to OpenStack Compute (nova).

Status in OpenStack Compute (Nova): New

Bug description: Recently while I was refactoring the smoke tests, I found that attach volume is reporting success even when the operation fails. I was able to work around this in the smoke tests by waiting longer before attaching. My initial sense is that the volume is reporting its state as "available" some small amount of time (5-15 seconds?) before it is really available.

Here is a snippet from the volume smoke tests that show how I was forced to work around the issue:

http://paste.openstack.org/show/100/