Bug 1876797
Summary: | The "Last Updated" status of Installed Operators is not displayed correctly in OCP 4.5. | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Asheth <asheth> |
Component: | OLM | Assignee: | Evan Cordell <ecordell> |
OLM sub component: | OLM | QA Contact: | Jian Zhang <jiazha> |
Status: | CLOSED DUPLICATE | Docs Contact: | |
Severity: | low | ||
Priority: | low | CC: | aos-bugs, jesusr, jokerman, krizza, nhale |
Version: | 4.5 | Keywords: | Reopened |
Target Milestone: | --- | ||
Target Release: | 4.7.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-02-01 16:00:37 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Asheth
2020-09-08 08:10:51 UTC
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 *** |