Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695198 - olm operator does not reset progressing transition timestamp when it upgrades
Summary: olm operator does not reset progressing transition timestamp when it upgrades
Keywords:
Status: CLOSED DUPLICATE of bug 1688611
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Evan Cordell
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-02 16:15 UTC by Clayton Coleman
Modified: 2019-04-03 01:45 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-03 01:45:13 UTC
Target Upstream Version:


Attachments (Terms of Use)

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


Note You need to log in before you can comment on or make changes to this bug.