Ohad, can someone from MS (or having the relevant knowledge) can own this BZ?
@muagarwa this BZ is a clone of an MS BZ where the fix needs to go into the product. The issue was identified as a wrongful configuration of the product's pod monitor configuration, more specifically the specificity of the selector on that pod monitor (which is too wide). I believe all of this information is available on the blocked MS BZ. The MS team has very little knowledge of the codebase for ocs-operator/odf-operator and it makes more sense to have the fix be issued by an OCS core team member.
Malay, can you please take a look
(In reply to Mudit Agarwal from comment #4) > Malay, can you please take a look Sure. @muagarwal I think this issue is not related to OCS but it should come under ODF Operator. So should we move it?
I think the issue pertains to this part in ODF Operator, https://github.com/red-hat-storage/odf-operator/blob/7d9c3025ae6011a7815d7c2fcc21ac0b7431569d/bundle/manifests/odf-operator-controller-manager-metrics-monitor_monitoring.coreos.com_v1_servicemonitor.yaml#L5. So let's move it there.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: Red Hat OpenShift Data Foundation 4.11.0 security, enhancement, & bugfix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:6156