Description of problem (please be detailed as possible and provide log snippests): ramen-hub-operator pod is restarting after creating subscription based busybox-rbd app on c1 managed cluster. I have observed this issue when odf is upgraded from 4.14.0-113 to 4.14.0-117 build. Logs- Version of all relevant components (if applicable): OCP- 4.14 ODF- 4.14.0-117 ACM- 2.9.0 ceph- 6.1 Does this issue impact your ability to continue to work with the product (please explain in detail what is the user impact)? Is there any workaround available to the best of your knowledge? No Rate from 1 - 5 the complexity of the scenario you performed that caused this bug (1 - very simple, 5 - very complex)? Can this issue reproducible? yes Can this issue reproduce from the UI? Yes If this is a regression, please provide more details to justify this: Steps to Reproduce: 1.Configure MDR cluster. 2.Upgraded ODF from 4.14.0-113 to 4.14.0-117 on all clusters. 3.Create subscription based app 4.Apply dr policy 5.check ramen-hub-operator pod status Actual results: Ramen-hub-operator pod is restarted. Expected results: Ramen-hub-operator pod should not restart Additional info:
Verified this issue with latest odf build 4.14.0-123 and no issue observed. hence marking it as verified. Verification Steps: 1.Upgraded ODF from 4.14.0-117 to 4.14.0-123 on all clusters. 2.Create subscription based app 3.Applied DRpolicy to app 4.check ramen-hub-operator pod status
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.14.0 security, enhancement & bug fix 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-2023:6832