[LU-16947] Make multiop_bg_pause send the kill signal to the correct pid Created: 06/Jul/23 Updated: 27/Jul/23 Resolved: 27/Jul/23 |
|
| Status: | Resolved |
| Project: | Lustre |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | Lustre 2.16.0 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Arshad Hussain | Assignee: | Arshad Hussain |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Severity: | 3 |
| Rank (Obsolete): | 9223372036854775807 |
| Description |
|
multiop_bg_pause under test-framework starts multiop in background and waits for signal if "_" option is provided. On 'verbose' mode the PAUSING string is printed on console which is checked and if not found error is reported by multiop_bg_pause function. On error, it is required to kill the existing running multiop binary as if not done will eventually timeout and not exit the test. Currently on error multiop_bg_pause function incorrectly sends singlal to wrong PID. |
| Comments |
| Comment by Gerrit Updater [ 06/Jul/23 ] |
|
"Arshad Hussain <arshad.hussain@aeoncomputing.com>" uploaded a new patch: https://review.whamcloud.com/c/fs/lustre-release/+/51589 |
| Comment by Gerrit Updater [ 27/Jul/23 ] |
|
"Oleg Drokin <green@whamcloud.com>" merged in patch https://review.whamcloud.com/c/fs/lustre-release/+/51589/ |
| Comment by Peter Jones [ 27/Jul/23 ] |
|
Landed for 2.16 |