tempest

  1. Bug #1316926
  2. Comment #1

Comment 1 for bug 1316926

Revision history for this message
clayg (clay-gerrard) wrote : Re: failed to reach ACTIVE status and task state "None" within the required time

So I see a lot of these status timeout messages, and there's a number of bugs open, the most popular of course being:

https://code.launchpad.net/bugs/1254890

How should we be grouping or classifying them? Are they all the same issue? What should we be looking for?

I hit one in 'tempest.api.compute.v3.servers.test_servers.ServersV3Test.test_create_specify_keypair'

... that like this bug report was:

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

http://logs.openstack.org/85/91685/2/gate/gate-tempest-dsvm-full/c83e2e3/console.html#_2014-05-09_06_34_10_221

I always keep thinking it's a libvirt thing:

http://logs.openstack.org/85/91685/2/gate/gate-tempest-dsvm-full/c83e2e3/logs/libvirtd.txt.gz#_2014-05-09_06_12_09_582

Those errors in libvirt where it says failed to read from the monitor do seem to bubble out as errors in n-cpu:

http://logs.openstack.org/85/91685/2/gate/gate-tempest-dsvm-full/c83e2e3/logs/screen-n-cpu.txt.gz?level=ERROR

What else can we look to?