Bug #46686
ERROR: setUpClass (tasks.mgr.dashboard.test_perf_counters.PerfCountersControllerTest)
Status:
New
Priority:
Normal
Assignee:
Laura Paduano
Category:
Testing - API
Target version:
-
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2020-07-23 06:26:36,824.824 INFO:__main__:====================================================================== 2020-07-23 06:26:36,824.824 INFO:__main__:ERROR: setUpClass (tasks.mgr.dashboard.test_perf_counters.PerfCountersControllerTest) 2020-07-23 06:26:36,824.824 INFO:__main__:---------------------------------------------------------------------- 2020-07-23 06:26:36,824.824 INFO:__main__:Traceback (most recent call last): 2020-07-23 06:26:36,825.825 INFO:__main__: File "/home/jenkins-build/build/workspace/ceph-dashboard-pr-backend/qa/tasks/mgr/dashboard/helper.py", line 150, in setUpClass 2020-07-23 06:26:36,825.825 INFO:__main__: cls._load_module("dashboard") 2020-07-23 06:26:36,825.825 INFO:__main__: File "/home/jenkins-build/build/workspace/ceph-dashboard-pr-backend/qa/tasks/mgr/mgr_test_case.py", line 157, in _load_module 2020-07-23 06:26:36,826.826 INFO:__main__: cls.wait_until_true(has_restarted, timeout=30) 2020-07-23 06:26:36,826.826 INFO:__main__: File "/home/jenkins-build/build/workspace/ceph-dashboard-pr-backend/qa/tasks/ceph_test_case.py", line 194, in wait_until_true 2020-07-23 06:26:36,826.826 INFO:__main__: raise RuntimeError("Timed out after {0}s".format(elapsed)) 2020-07-23 06:26:36,826.826 INFO:__main__:RuntimeError: Timed out after 30s 2020-07-23 06:26:36,826.826 INFO:__main__: 2020-07-23 06:26:36,826.826 INFO:__main__:---------------------------------------------------------------------- 2020-07-23 06:26:36,826.826 INFO:__main__:Ran 116 tests in 2136.427s
https://jenkins.ceph.com/job/ceph-dashboard-pr-backend/4199/
History
#1 Updated by Josh Durgin over 3 years ago
It seems these timeouts are still too low - here's one failing at 60s:
https://jenkins.ceph.com/job/ceph-api/211/
2020-08-05 17:21:05,811.811 INFO:__main__:---------------------------------------------------------------------- 2020-08-05 17:21:05,812.812 INFO:__main__:Traceback (most recent call last): 2020-08-05 17:21:05,812.812 INFO:__main__: File "/home/jenkins-build/build/workspace/ceph-api/qa/tasks/mgr/dashboard/helper.py", line 191, in setUp 2020-08-05 17:21:05,812.812 INFO:__main__: self.wait_for_health_clear(self.TIMEOUT_HEALTH_CLEAR) 2020-08-05 17:21:05,812.812 INFO:__main__: File "/home/jenkins-build/build/workspace/ceph-api/qa/tasks/ceph_test_case.py", line 162, in wait_for_health_clear 2020-08-05 17:21:05,812.812 INFO:__main__: self.wait_until_true(is_clear, timeout) 2020-08-05 17:21:05,812.812 INFO:__main__: File "/home/jenkins-build/build/workspace/ceph-api/qa/tasks/ceph_test_case.py", line 194, in wait_until_true 2020-08-05 17:21:05,812.812 INFO:__main__: raise RuntimeError("Timed out after {0}s".format(elapsed)) 2020-08-05 17:21:05,812.812 INFO:__main__:RuntimeError: Timed out after 60s
Is there any harm in increasing these sorts of timeouts dramatically (e.g. to 15 minutes) so the tests can pass? A cluster failing to become healthy eventually is not a common case given enough time.
#2 Updated by Ernesto Puerta almost 3 years ago
- Project changed from mgr to Dashboard
- Category changed from API Tests to Testing - API