yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem@xxxxxxxxxx>]

For example, when this failed in the log link above, around time
21:44:09.859, you can see in dstat that ceilometer agent notification
was really impacting the CPU:

http://logs.openstack.org/08/92608/1/gate/gate-tempest-dsvm-postgres-
full/57b137a/logs/dstat.txt.gz

09-05 21:44:09| 68  14  16   1   0   1|3933M  184M 2529M  837M|   0
0 |  48k 7780k|5.00   192 |4588  8707 |8.20 6.81 3.49| 13   0  52
|ceilometer-agent-noti2052 7.5%3552B  97k

It'd be cool if we could dynamically adjust timeouts based on current
system load...but maybe that's just overly complicating things - the
alternative is probably just making ceilometer better and consuming less
CPU all the time.

** Also affects: ceilometer
   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/1320617

Title:
  failed to reach ACTIVE status within the required time (196 s).
  Current status: SAVING

Status in OpenStack Telemetry (Ceilometer):
  New
Status in OpenStack Compute (Nova):
  New

Bug description:
  http://logs.openstack.org/08/92608/1/gate/gate-tempest-dsvm-postgres-
  full/57b137a/console.html.gz

  The relevant part of the test case:
  1. Boot servet1
  2. Boot server2 wait until active
  3. wait until server1 ACTIVE
  4. Create snapshot from server1, wait until ACTIVE with 196 sec timeout
  5. Cleanup, die with the first failure

  Normally the test case would create 2 additional image at the beginning,
  but now died at fist image creation.

  2014-05-09 21:44:09.857 | Captured traceback:
  2014-05-09 21:44:09.858 | ~~~~~~~~~~~~~~~~~~~
  2014-05-09 21:44:09.858 |     Traceback (most recent call last):
  2014-05-09 21:44:09.858 |       File "tempest/api/compute/images/test_list_image_filters.py", line 45, in setUpClass
  2014-05-09 21:44:09.858 |         cls.server1['id'], wait_until='ACTIVE')
  2014-05-09 21:44:09.858 |       File "tempest/api/compute/base.py", line 302, in create_image_from_server
  2014-05-09 21:44:09.858 |         kwargs['wait_until'])
  2014-05-09 21:44:09.858 |       File "tempest/services/compute/xml/images_client.py", line 140, in wait_for_image_status
  2014-05-09 21:44:09.858 |         waiters.wait_for_image_status(self, image_id, status)
  2014-05-09 21:44:09.858 |       File "tempest/common/waiters.py", line 129, in wait_for_image_status
  2014-05-09 21:44:09.858 |         raise exceptions.TimeoutException(message)
  2014-05-09 21:44:09.859 |     TimeoutException: Request timed out
  2014-05-09 21:44:09.859 |     Details: (ListImageFiltersTestXML:setUpClass) Image 20b6e7a9-f65d-4d17-b025-59f9237ff8cb failed to reach ACTIVE status within the required time (196 s). Current status: SAVING.

  logstash:
  http://logstash.openstack.org/#eyJzZWFyY2giOiJtZXNzYWdlOlwiZmFpbGVkIHRvIHJlYWNoIEFDVElWRSBzdGF0dXMgd2l0aGluIHRoZSByZXF1aXJlZCB0aW1lXCIgQU5EIGZpbGVuYW1lOlwiY29uc29sZS5odG1sXCIgQU5EIG1lc3NhZ2U6XCJDdXJyZW50IHN0YXR1czogU0FWSU5HXCIiLCJmaWVsZHMiOltdLCJvZmZzZXQiOjAsInRpbWVmcmFtZSI6ImFsbCIsImdyYXBobW9kZSI6ImNvdW50IiwidGltZSI6eyJ1c2VyX2ludGVydmFsIjowfSwic3RhbXAiOjE0MDA0MTEyNDcwMzksIm1vZGUiOiIiLCJhbmFseXplX2ZpZWxkIjoiIn0=

  message:"failed to reach ACTIVE status within the required time" AND
  filename:"console.html" AND message:"Current status: SAVING"

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