Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1695198

Summary:	olm operator does not reset progressing transition timestamp when it upgrades
Product:	OpenShift Container Platform	Reporter:	Clayton Coleman <ccoleman>
Component:	OLM	Assignee:	Evan Cordell <ecordell>
Status:	CLOSED DUPLICATE	QA Contact:	Jian Zhang <jiazha>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0
Target Milestone:	---
Target Release:	---
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:	2019-04-03 01:45:13 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Clayton Coleman 2019-04-02 16:15:05 UTC

During an upgrade, operators are required to update the lastTransitionTimestamp of Progressing when they start upgrading and when they complete.  If there is no need to set progressing, the last transition time should still be reset at the end of an upgrade when they hit "level".

When I started an upgrade (39m ago was the beginning) I see:

clusteroperator.config.openshift.io/operator-lifecycle-manager           0.0.1                          True        False         False     56m
clusteroperator.config.openshift.io/operator-lifecycle-manager-catalog   0.0.1                          True        False         False     56m

which means the operator did not reset progressing lastTransitionTime

This value is used to tell the admin when "something happened" and an upgrade is "something".

Comment 1 Clayton Coleman 2019-04-02 17:36:48 UTC

https://github.com/openshift/cluster-version-operator/pull/154 will document this and an e2e test will verify it in the future post-upgrade