Bug #39598
[test] possible race condition in rbd-nbd disconnect
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
luminous,mimic,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
The "rbd-nbd unmap" command just sends a disconnect request to the "rbd-nbd" process and exits. If this is immediately followed with a "rbd-nbd list-mapped", it might still locate the disconnected process. Therefore, internally delay the "unmap" to give the process time to exit.
Related issues
History
#1 Updated by Jason Dillaman almost 5 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
#2 Updated by Jason Dillaman almost 5 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 27981
#3 Updated by Mykola Golub almost 5 years ago
- Status changed from Fix Under Review to Pending Backport
#4 Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #39673: luminous: [test] possible race condition in rbd-nbd disconnect added
#5 Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #39674: mimic: [test] possible race condition in rbd-nbd disconnect added
#6 Updated by Nathan Cutler almost 5 years ago
- Copied to Backport #39675: nautilus: [test] possible race condition in rbd-nbd disconnect added
#7 Updated by Nathan Cutler over 4 years 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".