yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

*** This bug is a duplicate of bug 1255624 ***
    https://bugs.launchpad.net/bugs/1255624

Public bug reported:

Failed here:

http://logs.openstack.org/79/96679/6/check/check-tempest-dsvm-postgres-
full/e2050f1/console.html

2014-06-12 17:01:03.997 | tempest.scenario.test_server_advanced_ops.TestServerAdvancedOps.test_server_sequence_suspend_resume[compute]
2014-06-12 17:01:03.997 | ------------------------------------------------------------------------------------------------------------
2014-06-12 17:01:03.998 | 
2014-06-12 17:01:03.998 | Captured traceback:
2014-06-12 17:01:03.998 | ~~~~~~~~~~~~~~~~~~~
2014-06-12 17:01:03.998 |     Traceback (most recent call last):
2014-06-12 17:01:03.998 |       File "tempest/test.py", line 126, in wrapper
2014-06-12 17:01:03.998 |         return f(self, *func_args, **func_kwargs)
2014-06-12 17:01:03.998 |       File "tempest/scenario/test_server_advanced_ops.py", line 87, in test_server_sequence_suspend_resume
2014-06-12 17:01:03.999 |         'SUSPENDED')
2014-06-12 17:01:03.999 |       File "tempest/scenario/manager.py", line 190, in status_timeout
2014-06-12 17:01:03.999 |         not_found_exception=not_found_exception)
2014-06-12 17:01:03.999 |       File "tempest/scenario/manager.py", line 253, in _status_timeout
2014-06-12 17:01:03.999 |         raise exceptions.TimeoutException(message)
2014-06-12 17:01:03.999 |     TimeoutException: Request timed out
2014-06-12 17:01:04.000 |     Details: Timed out waiting for thing bffbe5f7-c0db-4c74-9f71-a44bcd473820 to become SUSPENDED


When it times out, the server was still in ACTIVE state, so it's like
the suspend call never did anything:

Waiting for <Server: scenario-server--1865968309> to get to SUSPENDED
status. Currently in ACTIVE status

We could probably improve the logging there to see what the task_state
is when this fails.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: libvirt testing

** Tags added: testing

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

Title:
  test_server_sequence_suspend_resume times out waiting for thing to
  become SUSPENDED

Status in OpenStack Compute (Nova):
  New

Bug description:
  Failed here:

  http://logs.openstack.org/79/96679/6/check/check-tempest-dsvm-
  postgres-full/e2050f1/console.html

  2014-06-12 17:01:03.997 | tempest.scenario.test_server_advanced_ops.TestServerAdvancedOps.test_server_sequence_suspend_resume[compute]
  2014-06-12 17:01:03.997 | ------------------------------------------------------------------------------------------------------------
  2014-06-12 17:01:03.998 | 
  2014-06-12 17:01:03.998 | Captured traceback:
  2014-06-12 17:01:03.998 | ~~~~~~~~~~~~~~~~~~~
  2014-06-12 17:01:03.998 |     Traceback (most recent call last):
  2014-06-12 17:01:03.998 |       File "tempest/test.py", line 126, in wrapper
  2014-06-12 17:01:03.998 |         return f(self, *func_args, **func_kwargs)
  2014-06-12 17:01:03.998 |       File "tempest/scenario/test_server_advanced_ops.py", line 87, in test_server_sequence_suspend_resume
  2014-06-12 17:01:03.999 |         'SUSPENDED')
  2014-06-12 17:01:03.999 |       File "tempest/scenario/manager.py", line 190, in status_timeout
  2014-06-12 17:01:03.999 |         not_found_exception=not_found_exception)
  2014-06-12 17:01:03.999 |       File "tempest/scenario/manager.py", line 253, in _status_timeout
  2014-06-12 17:01:03.999 |         raise exceptions.TimeoutException(message)
  2014-06-12 17:01:03.999 |     TimeoutException: Request timed out
  2014-06-12 17:01:04.000 |     Details: Timed out waiting for thing bffbe5f7-c0db-4c74-9f71-a44bcd473820 to become SUSPENDED


  When it times out, the server was still in ACTIVE state, so it's like
  the suspend call never did anything:

  Waiting for <Server: scenario-server--1865968309> to get to SUSPENDED
  status. Currently in ACTIVE status

  We could probably improve the logging there to see what the task_state
  is when this fails.

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