Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem (please be detailed as possible and provide log snippests): ====================================================================== Sharing the snip of the discussions we are having since past few days on Recipe Operator getting auto-installed when ODF operator is installed - irresepctive of it being an internal, external or provider/client mode or DR 1. What is the recipe operator? It has operator in the name because of Red Hat build conventions but it is only a bundle that installs the Recipe CRD that is required by DR applications. 2. Who is installing it? Odf-operator installs it along with the ODF installation. 3. Why is odf-operator installing it if it is DR related? Because applications that require DR create the recipe CR along with the application definition even before enabling DR for the application. When such applications are deployed using ACM the deployment fails if the CRD isn’t available in the system. If DR isn’t enabled in the system, the recipe CR is not read/operated on by anyone. The CR itself will be in the application namespace so it won’t confuse anyone else. 4. Can the operator be hidden? Yes, I don’t see a problem with hiding it. 5. UI tooltip required? If hidden, I don’t think we need any UI changes for it. 6. Doc changes? I think if there is a section where we list what all odf-operator installation brings, then adding a line/bullet there to describe the recipe CRD would be useful. Description from the recipe CRD can be copied/used. ``` Recipe describes a workflow used for capturing or recovering Kubernetes resources. This can be referred to by a Ramen DRPlacementControl object when kubeObjectProtection is enabled. Version of all relevant components (if applicable): ================================================== odf 4.16 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? 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? Can this issue reproduce from the UI? If this is a regression, please provide more details to justify this: Steps to Reproduce: 1. Install ODF operator 2. Check the Installed Operators page 3. Configure DR and again check the Installed Operators page Actual results: ================ Recipe operator is listed in the installed operator page post odf operator installation Expected results: ================= Recipe operator can be hidden and should show up only when DR is configured Additional info:
Hello Neha, We can not hide/show it based on the installations. It is either always hide or always show. I have sent a PR for now to hide it. As it does not have any controller and I don't see any value in showing it.
(In reply to Nitin Goyal from comment #3) > Hello Neha, We can not hide/show it based on the installations. It is either > always hide or always show. I have sent a PR for now to hide it. As it does > not have any controller and I don't see any value in showing it. Ack on hiding based on discussions with Talur, Karolin and other qe folks
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.16.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-2024:4591