+++ This bug was initially created as a clone of Bug #1848729 +++
+++ This bug was initially created as a clone of Bug #1847672 +++
Description of problem:
Changing the readiness or liveness probe integer fields (initialDelaySeconds, periodSeconds, failureThreshold, and timeoutSeconds) of an operator deployment manifest aren't being applied to operator deployment resources during upgrades.
Commit new probe timeout values for a CVO-managed operator, e.g. https://github.com/openshift/machine-config-operator/pull/1818.
On a new installation, the correct values are applied; but when performing a Y or Z upgrade to the new commit, the new values are not applied to the deployment.
The new values should be applied during an upgrade.
--- Additional comment from firstname.lastname@example.org on 2020-06-16 18:56:44 UTC ---
This blocks a fix for quorum-guard which involves changing probe timeout values (https://bugzilla.redhat.com/show_bug.cgi?id=1829923).
We do not have time to fix the bug in this sprint as we are working on higher priority bugs and features. Hence we are adding UpcomingSprint now, and we'll revisit this in the next sprint.
*** Bug 1849619 has been marked as a duplicate of this bug. ***
Opened https://github.com/openshift/cluster-version-operator/pull/391 for this
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.