Actions
Bug #64011
openqa: Command failed qa/workunits/suites/pjd.sh
Status:
Triaged
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
qa-suite
Labels (FS):
qa, qa-failure
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
2024-01-11T06:33:41.517 ERROR:tasks.mds_thrash.fs.[a]:exception: Traceback (most recent call last): File "/home/teuthworker/src/github.com_ceph_ceph-c_4bcedb9fc11bed1fd6fd0c4fd59187401f309680/qa/tasks/mds_thrash.py", line 124, in _run self.do_thrash() File "/home/teuthworker/src/github.com_ceph_ceph-c_4bcedb9fc11bed1fd6fd0c4fd59187401f309680/qa/tasks/mds_thrash.py", line 312, in do_thrash status = self.wait_for_stable(rank, gid) File "/home/teuthworker/src/github.com_ceph_ceph-c_4bcedb9fc11bed1fd6fd0c4fd59187401f309680/qa/tasks/mds_thrash.py", line 217, in wait_for_stable raise RuntimeError('timeout waiting for cluster to stabilize') RuntimeError: timeout waiting for cluster to stabilize
Updated by Venky Shankar 4 months ago
- Category set to Correctness/Safety
- Status changed from New to Triaged
- Assignee set to Milind Changire
- Target version set to v19.0.0
Could be that the mds was busy in replay state. Needs to be looked into.
Actions