Actions
Bug #50734
closed[pwl][test] make recovery.yaml actually trigger recovery
% Done:
0%
Source:
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
- "timeout 10s rbd bench --io-pattern rand --io-type write testimage || true" - "rbd bench --io-type write --io-pattern rand --io-total 32M testimage"
doesn't do it because "rbd bench" will catch timeout's TERM signal...
Updated by Deepika Upadhyay over 2 years ago
@majinpeng @CONGMIN YIN did you have context around this by any change?
Updated by CONGMIN YIN over 2 years ago
I tried, will submit fix soon, just set SIGKILL is OK.
timeout -s SIGKILL 10s rbd bench --io-pattern rand --io-type write test/image2
Updated by CONGMIN YIN over 2 years ago
- Status changed from In Progress to Fix Under Review
- Assignee changed from Ilya Dryomov to CONGMIN YIN
Updated by Ilya Dryomov almost 2 years ago
- Status changed from Fix Under Review to Pending Backport
- Backport changed from pacific to pacific,quincy
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56582: pacific: [pwl][test] make recovery.yaml actually trigger recovery added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56583: quincy: [pwl][test] make recovery.yaml actually trigger recovery added
Updated by Backport Bot about 1 year ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".
Actions