Created attachment 1814828 [details] ODF Operator Card Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Go to 'OperatorHub' and search for OpenShift Data Foundation 2.Click on the card as we do for installation. 3. Notice that the details for repository, container image, support etc. are set to N/A and are missing. Actual results: Details for repository, container image, support etc. are set to N/A on the card while installing ODF Operator. Expected results: Add all the relevant details. Additional info:
*** Bug 2000533 has been marked as a duplicate of this bug. ***
Nitin has it right, you are only linking to mock-ups, none of this information was ever actually in the bundle itself. We need PRs (and BZs) to update the CSV description if anything is missing. My guess would be we'd need to copy over most of the ocs-operator description, since ocs-operator is no longer visible in the UI, but we don't have any solid requirements at this time.
Hi Tested with ODF version "4.9.0-158.ci" and OCP 4.9. The detail card has all the information related to repo, version, source ,provider but i need guidance with the description that is around "OpenShift Data Foundation operator" ,OpenShift Data Foundation console and "Core Capabilities". Do we need to add anything more in the detail card or these description? 4.9 ODF operator detail card is attached in comment#14
Hi Yuval Request you for clarification on the comment#15 and comment#16 . Thanks Mugdha
so I'm very sorry for the very late response, so after discussing this topic with Eran he said that he wants to keep the same text we had for OCS and just change OCS to ODF in all places. see the design: https://marvelapp.com/prototype/g1h86ga/screen/78847977
@
*** Bug 2018199 has been marked as a duplicate of this bug. ***
Hi Eran and Aman Following steps were performed :- 1. Created an OCP 4.9 cluster via jenkins . 2. Created a catalogsoure.yaml with the latest ODF version ##[root@localhost doc]# cat catalogsource.yaml apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: labels: ocs-operator-internal: 'true' name: redhat-operators namespace: openshift-marketplace spec: displayName: Openshift Data Foundation icon: base64data: '' mediatype: '' image: quay.io/rhceph-dev/ocs-registry:4.9.0-237.ci priority: 100 publisher: Red Hat sourceType: grpc updateStrategy: registryPoll: interval: 15m 3. Logged into the console and directedtowards operator hub. ** Information was missing as compared to https://marvelapp.com/prototype/g1h86ga/screen/78847977(screenshot for the same is attached in comment #24) Please guide me here ! Thanks Mugdha
I can jump in in this one: I chatted with Eran over DM and the current stopgap is to ship with what was in the PR as-is. This is immensely low priority and not worth holding up the release. I'm going to move the bug back to ON_QA, we'll do a more thorough rewrite in 4.9.z.
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 (Moderate: Red Hat OpenShift Data Foundation 4.9.0 enhancement, security, and 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-2021:5086