Description of problem: The "Last Updated" status of Installed Operators is not displayed correctly in OCP 4.5. Version-Release number of selected component (if applicable): OCP 4.5 How reproducible: 1. Install two operators for example ElasticSearch operator and Red Hat OpenShift Jaeger operators. While installing these Operators, specify the installation mode as "All Namespaces on the cluster". 2. View the "Last Updated" status of these operators. when selected "All Projects", it should display the "Last Updated" time properly. However, when selected a particular namespace for example "kube-system or the other namespace, it displays incorrect "Last Updated" time. Steps to Reproduce: 1. Log in to OpenShift Web-Console. 2. Install two operators for example ElasticSearch operator and Red Hat OpenShift Jaeger operators. While installing these Operators, specify the installation mode as "All Namespaces on the cluster". 3. View the "Last Updated" status of these operators. when selected "All Projects", it should display the "Last Updated" time properly. However, when selected a particular namespace for example "kube-system or the other namespace, it displays incorrect "Last Updated" time. Actual results: The "Last Updated" time shows different/incorrect value when viewed from a particular namespace as compared to when viewed from the "All Namespaces". Expected results: The "Last Updated" time should show the same output/value when viewed from a particular namespace as compared to when viewed from the "All Namespaces". Additional info:
When an operator is installed in all namespaces, the "source" CSV is created in openshift-operators namespace and the CSV is cloned in all other namespaces. The lastUpdateTime status field on the "cloned" CSVs is not updated whenever the source CSV changes in an inconsequential way and hence they have different values. I confirmed with Kevin and Nick from OLM team and they don't want to change this behavior. Hence closing this as won't fix
Discussed further with Nick from the OLM team and decided that it would be fixed on the OLM side
We are having the same issue in OCP 4.6. Can we fix it for 4.6 as well?
For an unrelated performance reason, this bug was resolved in https://bugzilla.redhat.com/show_bug.cgi?id=1910401. Marking this as a duplicate and closing. *** This bug has been marked as a duplicate of bug 1910401 ***