tempest

  1. Bug #1316926
  2. Comment #2

Comment 2 for bug 1316926

Revision history for this message
Attila Fazekas (afazekas) wrote : Re: failed to reach ACTIVE status and task state "None" within the required time

In this case http://logs.openstack.org/32/97532/3/check/check-tempest-dsvm-postgres-full/0ca8157/console.html

It is very likely the https://github.com/openstack/nova/blob/c07626012e35c03da37ea3ed1b5ddf2dea352522/nova/compute/manager.py#L1754 is reached ('Instance spawned successfully', ), but the
https://github.com/openstack/nova/blob/c07626012e35c03da37ea3ed1b5ddf2dea352522/nova/compute/manager.py#L1789 is not.

http://logs.openstack.org/32/97532/3/check/check-tempest-dsvm-postgres-full/0ca8157/logs/screen-n-cpu.txt.gz#_2014-06-10_00_28_03_644
2014-06-10 00:28:03.644 32494 INFO nova.virt.libvirt.driver [-] [instance: f4ef7a2f-641f-463a-a922-009bed8284ed] Instance spawned successfully.
2014-06-10 00:28:03.663 DEBUG nova.compute.manager [req-bb4f648f-4b18-4f0d-9155-584ba7391b02 ServersAdminTestJSON-407950993 ServersAdminTestJSON-821753686] [instance: f4ef7a2f-641f-463a-a922-009bed8284ed] Checking state _get_power_state /opt/stack/new/nova/nova/compute/manager.py:1067