Actions
Bug #44567
closed[test] NBD workunit does not wait for unmap disconnect delay
Status:
Resolved
Priority:
Normal
Assignee:
Jason Dillaman
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
luminous,mimic,nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Description
After unmapping a volume, it might take some time for the disconnect signal to be sent to the backing daemon. This can result in "rbd-nbd list-mapped" or "rbd-nbd map /dev/<same nbd device>" commands incorrectly failing in the test case. All "unmap" actions in the test should wait for the device to disappear from "list-mapped" before proceeding (timeout if it fails to every unmap).
Updated by Jason Dillaman about 4 years ago
- Status changed from New to In Progress
- Assignee set to Jason Dillaman
Updated by Jason Dillaman about 4 years ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 33898
Updated by Mykola Golub about 4 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #44646: luminous: [test] NBD workunit does not wait for unmap disconnect delay added
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #44647: mimic: [test] NBD workunit does not wait for unmap disconnect delay added
Updated by Nathan Cutler about 4 years ago
- Copied to Backport #44648: nautilus: [test] NBD workunit does not wait for unmap disconnect delay added
Updated by Shyukri Shyukriev almost 4 years ago
- Status changed from Pending Backport to Need More Info
Original PR is targeting octopus.
Updated by Jason Dillaman almost 4 years ago
- Status changed from Need More Info to Pending Backport
The Octopus branch was being periodically merged back into the master branch at the time.
Updated by Nathan Cutler almost 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".
Actions