Project

General

Profile

Actions

Bug #15474

closed

Blacklisting a client results in ESHUTDOWN respond code instead of EBLACKLISTED

Added by Jason Dillaman about 8 years ago. Updated about 8 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Jason Dillaman
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

librbd uses the "-EBLACKLISTED" error code to detect when a client has been blacklisted so it can shut down in an orderly fashion. ReplicatedPG.cc is setting the error code correctly, but it appears to be getting overwritten.

2016-04-12 11:08:55.145124 7fea309f8700 10 osd.0 pg_epoch: 69 pg[0.0( v 68'5887 (61'2800,68'5887] local-les=67 n=30 ec=1 les/c/f 67/67/0 66/66/66) [0,2,1] r=0 lpr=66 luod=68'5885 lua=68'5885 crt=68'5883 lcod 68'5884 mlcod 68'5884 active+clean] do_op 127.0.0.1:0/4189953352 is blacklisted
2016-04-12 11:08:55.145136 7fea309f8700  1 -- 127.0.0.1:6800/3046 --> 127.0.0.1:0/4189953352 -- osd_op_reply(8872 rbd_data.85362ae8944a.00000000000000b9 [stat,write 3788800~4096] v0'0 uv0 ondisk = -108 ((108) Cannot send after transport endpoint shutdown)) v7 -- ?+0 0x55a9ff9fad00 con 0x55a9fe5efc80
Actions #1

Updated by Jason Dillaman about 8 years ago

  • Status changed from In Progress to Rejected

Cancel that -- EBLACKLISTED is just a #define for ESHUTDOWN

Actions

Also available in: Atom PDF