← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1328293] [NEW] tempest test_delete_server_while_in_attached_volume fails Invalid volume status available/error

 

Public bug reported:

This keystone change [1] failed with an error in the
tempest.api.compute.servers.test_delete_server.DeleteServersTestXML.test_delete_server_while_in_attached_volume
test in the gate-tempest-dsvm-full job.

Here's the log:

http://logs.openstack.org/45/84945/13/gate/gate-tempest-dsvm-
full/600e742/console.html.gz#_2014-06-06_18_53_45_253

The error tempest reports is

 Details: Volume None failed to reach in-use status within the required
time (196 s).

So it's waiting for the volume to reach a status which it doesn't get to
in 196 s. Looks like the volume is in "attaching" status.

So maybe tempest isn't waiting long enough, or nova / cinder is hung or
just takes too long?

There's also a problem in that tempest says the volume is None when it
should be the volume ID (49fbde74-6e6a-4781-a271-787aa2deb674)

[1] https://review.openstack.org/#/c/84945/

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  tempest test_delete_server_while_in_attached_volume fails Invalid
  volume status available/error

Status in OpenStack Compute (Nova):
  New

Bug description:
  This keystone change [1] failed with an error in the
  tempest.api.compute.servers.test_delete_server.DeleteServersTestXML.test_delete_server_while_in_attached_volume
  test in the gate-tempest-dsvm-full job.

  Here's the log:

  http://logs.openstack.org/45/84945/13/gate/gate-tempest-dsvm-
  full/600e742/console.html.gz#_2014-06-06_18_53_45_253

  The error tempest reports is

   Details: Volume None failed to reach in-use status within the
  required time (196 s).

  So it's waiting for the volume to reach a status which it doesn't get
  to in 196 s. Looks like the volume is in "attaching" status.

  So maybe tempest isn't waiting long enough, or nova / cinder is hung
  or just takes too long?

  There's also a problem in that tempest says the volume is None when it
  should be the volume ID (49fbde74-6e6a-4781-a271-787aa2deb674)

  [1] https://review.openstack.org/#/c/84945/

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


Follow ups

References