Bug 2132366

Summary: Remove workaround to restart RBD mirror daemon every hour in the ceph cluster config
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Shyamsundar <srangana>
Component: ocs-operatorAssignee: Mudit Agarwal <muagarwa>
Status: CLOSED CURRENTRELEASE QA Contact: Pratik Surve <prsurve>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.12CC: amagrawa, idryomov, kramdoss, kseeger, mrajanna, muagarwa, ocs-bugs, odf-bz-bot, sostapov, tnielsen
Target Milestone: ---   
Target Release: ODF 4.12.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 4.12.0-74 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-08 14:06:28 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 Shyamsundar 2022-10-05 12:11:27 UTC
Description of problem (please be detailed as possible and provide log
snippests):

A workaround to restart the mirror daemon was added to the ocs-operator code, or more specifically to set 'rbd_mirror_die_after_seconds' to 3600 seconds. This was done as mirror daemon needed a restart to clear state and allow further mirroring due to issues in the mirroring code.

These issues are now fixed in Ceph and as a result the workaround/setting needs to be removed from the product as well.

PR introducing the change: https://github.com/red-hat-storage/ocs-operator/pull/1740
BZ introducing the change: https://bugzilla.redhat.com/show_bug.cgi?id=2093266

Version of all relevant components (if applicable):
Needs to be fixed 4.12 onward

Does this issue impact your ability to continue to work with the product
(please explain in detail what is the user impact)?
No


Is there any workaround available to the best of your knowledge?
NA


Rate from 1 - 5 the complexity of the scenario you performed that caused this
bug (1 - very simple, 5 - very complex)?
NA

Can this issue reproducible?
NA