Created attachment 1682582 [details] ArgoCD_CR_list_view_always_shows_Unknown_version Created attachment 1682582 [details] ArgoCD_CR_list_view_always_shows_Unknown_version On Operand list view, since “Version” is not a common spec field of Custom Resource ('spec.version'), it shouldn't be always present and only showing "Unknown", which makes UI look broken and in fact it doesn't. Version-Release number of selected component (if applicable): OCP 4.4 How reproducible: 100% Steps to Reproduce: 1. Go to “OperatorHub” view, install “ArgoCD” Operator 2. Go to “Installed Operators” view, create “ArgoCD” instance 3. See “ArgoCD” list view Actual results: See “ArgoCD” list view: “Version” field always show “Unknown” since 'spec.version’ doesn’t exist. Expected results: Shouldn’t be always showing 'spec.version’ field. Suggests removing the “Version” field and add “Created” field (from ‘metadata.creationTimestamp’ in YAML) as the right-most column.
We can look at a backport to 4.4.z.
Looked into the implementation and it turned out that the "Last Updated" field is already using the `obj.metadata.creationTimestamp` based on: https://github.com/openshift/console/blob/master/frontend/packages/operator-lifecycle-manager/src/components/operand/index.tsx#L170-L175 I would suggest to rename the field header to reflect on its data. Regarding the issue with the `Version` field I would either keep it as is or remove it complete. Ben thoughts ?
Nice! Didn't notice 'Last Updated' has been already there as tableColumnClasses[5] since it's not shown on the screens not wide enough. Agree on remove the non-gerneral `Version` field completely, and this would help expose the Last Updated timestamp on narrower res. Thanks!
+!
Created attachment 1690966 [details] Operand List View Now Operand List table only has Name, Kind, Status, Labels, Last Updated, Version column is removed Verified on 4.5.0-0.nightly-2020-05-21-135919
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, 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/RHBA-2020:2409