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".
Cloud credential operator, not dns. Cut and paste error.
https://github.com/openshift/cluster-version-operator/pull/154 will document this and an e2e test will verify it in the future post-upgrade
In tests I did upgrade from 4.0.0-0.nightly-2019-04-22-005059 to 4.0.0-0.nightly-2019-04-22-192613
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.