yahoo-eng-team team mailing list archive

[Joe Gordon <1316926@xxxxxxxxxxxxxxxxxx>]

It looks like this may be a libvirt bug, if so I am fairly sure we have
a duplicate of this somewhere

** Changed in: nova
       Status: New => Invalid

** Changed in: tempest
       Status: New => Invalid

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

Title:
  failed to reach ACTIVE status and task state "None" within the
  required time (196 s). Current status: BUILD. Current task state:
  spawning.

Status in OpenStack Compute (Nova):
  Invalid
Status in Tempest:
  Invalid

Bug description:
  Running test_reset_network_inject_network_info see a failure where
  unable to reach ACTIVE state.

  http://logs.openstack.org/71/91171/11/gate/gate-tempest-dsvm-
  full/8cf415d/console.html

  2014-05-07 03:33:22.910 | {3} tempest.api.compute.v3.admin.test_servers.ServersAdminV3Test.test_reset_network_inject_network_info [196.920138s] ... FAILED
  2014-05-07 03:33:22.910 | 
  2014-05-07 03:33:22.910 | Captured traceback:
  2014-05-07 03:33:22.910 | ~~~~~~~~~~~~~~~~~~~
  2014-05-07 03:33:22.910 |     Traceback (most recent call last):
  2014-05-07 03:33:22.910 |       File "tempest/api/compute/v3/admin/test_servers.py", line 170, in test_reset_network_inject_network_info
  2014-05-07 03:33:22.910 |         resp, server = self.create_test_server(wait_until='ACTIVE')
  2014-05-07 03:33:22.910 |       File "tempest/api/compute/base.py", line 233, in create_test_server
  2014-05-07 03:33:22.910 |         raise ex
  2014-05-07 03:33:22.910 |     TimeoutException: Request timed out
  2014-05-07 03:33:22.910 |     Details: Server 4491ab2f-2228-4d3f-b364-77d0276c18da failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: BUILD. Current task state: spawning.

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