Bug 1581449

Summary: [RFE] librbd/libcephfs/librgw should ignore rados_mon/osd_op_timeouts options
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vikhyat Umrao <vumrao>
Component: RADOSAssignee: Josh Durgin <jdurgin>
Status: CLOSED WONTFIX QA Contact: Manohar Murthy <mmurthy>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.5CC: bhubbard, ceph-eng-bugs, dzafman, kchai, mhackett, nojha
Target Milestone: rcKeywords: FutureFeature
Target Release: 4.*   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-13 21:23:48 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:

Description Vikhyat Umrao 2018-05-22 19:15:29 UTC 
Description of problem:
[RFE] librbd/libcephfs/librgw should ignore rados_mon/osd_op_timeouts options

Version-Release number of selected component (if applicable):
RHCS 3
RHCS 2.y
Comment 2 Brad Hubbard 2018-05-23 22:44:01 UTC 
If we are "making librbd/libcephfs/rgw ignore them" then this would not be a RADOS core change right? It would involve changes in the code that is *using* librados, not in librados itself, or am I missing something?
Comment 3 Vikhyat Umrao 2018-05-24 20:20:09 UTC 
(In reply to Brad Hubbard from comment #2)
> If we are "making librbd/libcephfs/rgw ignore them" then this would not be a
> RADOS core change right? It would involve changes in the code that is
> *using* librados, not in librados itself, or am I missing something?

I am not sure Brad. If that is the case I can split this RFE in three RFE's. Josh mentioned he wanted to add some safeguard to these options so that these three libraries cannot make use of these options.
Comment 4 Giridhar Ramaraju 2019-08-05 13:05:58 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 5 Giridhar Ramaraju 2019-08-05 13:08:42 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri