Bug 1503692

Summary:	tcmu-runner does not clean up its blacklisted entries upon recovery
Product:	[Red Hat Storage] Red Hat Ceph Storage	Reporter:	Jason Dillaman <jdillama>
Component:	iSCSI	Assignee:	Xiubo Li <xiubli>
Status:	CLOSED NEXTRELEASE	QA Contact:	Tejas <tchandra>
Severity:	medium	Docs Contact:	Bara Ancincova <bancinco>
Priority:	medium
Version:	3.0	CC:	anharris, ceph-eng-bugs, ceph-qe-bugs, hnallurv, kdreyer, sostapov, tchandra, xiubli
Target Milestone:	---
Target Release:	3.3z7
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	.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.	Story Points:	---
Clone Of:
Clones:	1805490 (view as bug list)		Environment:
Last Closed:	2020-12-16 19:23:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1805490
Bug Blocks:	1494421

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:

Comment 18 Yaniv Kaul 2020-07-16 13:35:01 UTC

Wasn't fixed for 3 years, and we believe we'll fix it in z7? Why not close it?