Bug 1503692 – tcmu-runner does not clean up its blacklisted entries upon recovery

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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:	NEW

Aliases:	None

Product:	Red Hat Ceph Storage
Classification:	Red Hat
Component:	iSCSI (Show other bugs)
Sub Component:
Version:	3.0
Hardware:	Unspecified Unspecified

Priority	medium Severity unspecified
Target Milestone:	rc
Target Release:	4.0
Assigned To:	Mike Christie
QA Contact:	Tejas
Docs Contact:	Bara Ancincova

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1494421
	Show dependency tree / graph

Reported:	2017-10-18 10:40 EDT by Jason Dillaman
Modified:	2018-10-18 13:07 EDT (History)
CC List:	4 users (show)

See Also:
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:
Environment:
Last Closed:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jason Dillaman 2017-10-18 10:40:05 EDT

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.