Invalid input received: Invalid volume: Volume status must be available or error, but current status is: creating

[Dolph Mathews]

A transient ERROR from a tempest run:

2014-07-07 04:48:43.757 ERROR nova.api.ec2 [req-6705e757-dc7c-4d8c-9b0d-f0a4e2ea363c EC2VolumesTest-1498681827 EC2VolumesTest-1461531536] Unexpected InvalidInput raised: Invalid input received: Invalid volume: Volume status must be available or error, but current status is: creating

Although this seems to have bubbled up to the console as:

  BadRequest: Invalid volume: Volume status must be available or error, but current status is: creating (HTTP 400)

Source: http://logs.openstack.org/36/103636/1/check/check-tempest-dsvm-full/b4d3e3c/

[Dolph Mathews (dolph)]

Could be a coincidence, but this looks like it might be isolated to HP build nodes.

e-r query: https://review.openstack.org/#/c/107485/

$ spandex queries/1342925.yaml
total hits: 15
build_status
  100% FAILURE
log_url
  13% http://logs.openstack.org/27/102827/3/check/check-tempest-dsvm-neutron-full/384a8a9/logs/screen-n-api.txt
  13% http://logs.openstack.org/91/91091/42/check/check-tempest-dsvm-postgres-full/a1fb4c3/logs/screen-n-api.txt
  13% http://logs.openstack.org/73/55873/14/check/check-tempest-dsvm-postgres-full/202dc75/logs/screen-n-api.txt
  13% http://logs.openstack.org/36/103636/1/check/check-tempest-dsvm-full/b4d3e3c/logs/screen-n-api.txt
  13% http://logs.openstack.org/83/98683/25/check/check-tempest-dsvm-postgres-full/280fe61/logs/screen-n-api.txt
  13% http://logs.openstack.org/67/106267/3/check/check-tempest-dsvm-full/f11b87a/logs/screen-n-api.txt
  13% http://logs.openstack.org/30/106630/1/check/check-tempest-dsvm-full/4e4d355/logs/screen-n-api.txt
  6% http://logs.openstack.org/70/104370/2/check/check-tempest-dsvm-postgres-full/5e04f4f/logs/screen-n-api.txt
loglevel
  100% ERROR
project
  26% openstack/nova
  13% openstack/horizon
  13% openstack/heat
  13% openstack/tempest
  13% openstack/sahara
  13% openstack/python-keystoneclient
  6% openstack/trove
build_change
  13% 91091
  13% 98683
  13% 106267
  13% 106630
  13% 55873
  13% 102827
  13% 103636
  6% 104370
build_node
  13% devstack-trusty-hpcloud-b3-752508
  13% devstack-trusty-hpcloud-b1-793634
  13% devstack-trusty-hpcloud-b1-765207
  13% devstack-trusty-hpcloud-b3-876506
  13% devstack-trusty-hpcloud-b1-810480
  13% devstack-trusty-hpcloud-b5-847328
  13% devstack-trusty-hpcloud-b3-866788
  6% devstack-trusty-hpcloud-b1-838450
module
  100% nova.api.ec2
filename
  100% logs/screen-n-api.txt
build_name
  46% check-tempest-dsvm-postgres-full
  40% check-tempest-dsvm-full
  13% check-tempest-dsvm-neutron-full
build_branch
  100% master
tags
  100% screen-n-api.txt screen oslofmt
build_queue
  100% check

[Sean Dague (sdague)]

Honestly, the ec2 state engine is a mess. Assume this is related to that.

[Andrey Pavlov (apavlov-e)]

this is not reproduced in stackforge/ec2-api project

[Matt Riedemann (mriedem)]

Haven't seen this in the gate in a long time, so marking incomplete.