Bug #20602: mon crush smoke test can time out under valgrind - RADOS - Ceph

Actions

Bug #20602

closed

mon crush smoke test can time out under valgrind

Added by Sage Weil almost 7 years ago. Updated almost 7 years ago.

Status:

Resolved

Priority:

Immediate

Assignee:

Category:

-

Target version:

-

% Done:

0%

Source:

Tags:

Backport:

Regression:

No

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(RADOS):

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

/a/sage-2017-07-12_02:32:14-rados-wip-sage-testing-distro-basic-smithi/1390174
rados/singleton-nomsgr/{all/valgrind-leaks.yaml rados.yaml}

2017-07-12T04:43:04.869 INFO:tasks.ceph:Creating RBD pool
2017-07-12T04:43:04.869 INFO:teuthology.orchestra.run.smithi033:Running: 'sudo ceph --cluster ceph osd pool create rbd 8'
2017-07-12T04:43:10.553 INFO:tasks.ceph.mon.a.smithi033.stderr:: timed out (5 sec)
2017-07-12T04:43:13.512 INFO:teuthology.orchestra.run.smithi033.stderr:Error ETIMEDOUT: crush test failed with -110: timed out during smoke test (5 seconds)

Related issues 1 (0 open — 1 closed)

Actions

#1

Updated by Sage Weil almost 7 years ago

Description updated (diff)

Actions

#2

Updated by Sage Weil almost 7 years ago

Priority changed from High to Urgent

/a/sage-2017-07-12_19:30:01-rados-wip-sage-testing-distro-basic-smithi/1392270
rados/singleton-nomsgr/{all/valgrind-leaks.yaml rados.yaml}

pretty reproducible, it seems!

Actions

#3

Updated by Sage Weil almost 7 years ago

Priority changed from Urgent to Immediate

/a/sage-2017-07-13_20:38:15-rados-wip-sage-testing-distro-basic-smithi/1397207

that's two consecutive runs for me..

Actions

#4

Updated by Kefu Chai almost 7 years ago

/a/kchai-2017-07-13_18:13:10-rados-wip-kefu-testing-distro-basic-smithi/1396642

rados/singleton-nomsgr/{all/valgrind-leaks.yaml rados.yaml}

Actions

#5

Updated by Sage Weil almost 7 years ago

A simple workaround would be to make a 'mon smoke test crush changes' option and turn it off when using valgrind.. what do you think?

Actions

#6

Updated by Sage Weil almost 7 years ago

Related to Bug #20601: mon comamnds time out due to pool create backlog w/ valgrind added

Actions

#7

Updated by Sage Weil almost 7 years ago

Valgrind is slow to do the fork and cleanup; that's why we keep timing out. Blame e189f11fcde6829cc7f86894b913bc1a3f81ecfe

Actions

#8

Updated by Sage Weil almost 7 years ago

Valgrind is slow to do the fork and cleanup; that's why we keep timing out. Blame e189f11fcde6829cc7f86894b913bc1a3f81ecfe

https://github.com/ceph/ceph/pull/16346

Actions

#9

Updated by Sage Weil almost 7 years ago

Status changed from 12 to Fix Under Review

Actions

#10

Updated by Kefu Chai almost 7 years ago

Status changed from Fix Under Review to Resolved
Assignee set to Sage Weil

Actions

Also available in: Atom PDF