Bug #50734
closed
[pwl][test] make recovery.yaml actually trigger recovery
Added by Ilya Dryomov almost 3 years ago.
Updated about 1 year ago.
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...
@majinpeng @CONGMIN YIN did you have context around this by any change?
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
- Status changed from In Progress to Fix Under Review
- Assignee changed from Ilya Dryomov to CONGMIN YIN
- Pull request ID set to 44217
- Status changed from Fix Under Review to Pending Backport
- Backport changed from pacific to pacific,quincy
- Copied to Backport #56582: pacific: [pwl][test] make recovery.yaml actually trigger recovery added
- Copied to Backport #56583: quincy: [pwl][test] make recovery.yaml actually trigger recovery added
- Tags set to backport_processed
- 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".
Also available in: Atom
PDF