Bug 1695204 - dns operator does not reset progressing transition timestamp when it upgrades
Summary: dns operator does not reset progressing transition timestamp when it upgrades
Keywords:
Status: CLOSED DUPLICATE of bug 1690342
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.1.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.1.0
Assignee: Daneyon Hansen
QA Contact: Hongan Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-02 16:19 UTC by Clayton Coleman
Modified: 2022-08-04 22:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-02 17:05:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Clayton Coleman 2019-04-02 16:19:43 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/dns                                  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 Daneyon Hansen 2019-04-02 17:05:20 UTC 

*** This bug has been marked as a duplicate of bug 1690342 ***
Note You need to log in before you can comment on or make changes to this bug.