Bug 1503692 - tcmu-runner does not clean up its blacklisted entries upon recovery
Summary: tcmu-runner does not clean up its blacklisted entries upon recovery
Status: ASSIGNED
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: iSCSI
Version: 3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: 4.1
Assignee: Mike Christie
QA Contact: Tejas
Bara Ancincova
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 1494421
TreeView+ depends on / blocked
 
Reported: 2017-10-18 14:40 UTC by Jason Dillaman
Modified: 2019-06-11 02:25 UTC (History)
5 users (show)

(edit)
.The `tcmu-runner` daemon does not clean up its blacklisted entries upon recovery

When the path fails over from the Active/Optimized to Active/Non-Optimized path or vice-versa on a failback, the old target is blacklisted to prevent stale writes from occurring. These blacklist entries are not cleaned up after the `tcmu-runner` daemon recovers from being blacklisted, resulting in extraneous blacklisted clients until the entries expire after one hour.
Clone Of:
(edit)
Last Closed:


Attachments (Terms of Use)

Description Jason Dillaman 2017-10-18 14:40:05 UTC
Description of problem:
When the path fails over from the Active/Optimized to Active/Non-Optimized path (or vice-versa on failback), the old target is blacklisted to prevent stale writes from occurring. These blacklist entries are not cleaned up after the tcmu-runner recovers from being blacklisted, resulting in an ever increasing list of blacklisted clients.

Version-Release number of selected component (if applicable):
1.3.x

How reproducible:
100%

Steps to Reproduce:
1. configure an initiator
2. block the Active/Optimized path to force an initiator failover
3. run "ceph osd blacklist ls" and see path is not removed

Actual results:
The blacklist entry is never removed -- it will only be removed after it times out.

Expected results:
The blacklist should be removed once the tcmu-runner daemon detects that it was blacklisted and recovers.

Additional info:


Note You need to log in before you can comment on or make changes to this bug.