Bug 1884464 - CVO marks an upgrade as failed when an operator takes more than 20 minutes to rollout
Summary: CVO marks an upgrade as failed when an operator takes more than 20 minutes to...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.z
Assignee: Scott Dodson
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On: 1884334
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-10-02 04:34 UTC by OpenShift BugZilla Robot
Modified: 2020-10-25 16:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-25 16:01:46 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description OpenShift BugZilla Robot 2020-10-02 04:34:37 UTC 
+++ This bug was initially created as a clone of Bug #1884334 +++

This bug was initially created as a copy of Bug #1862524

I am copying this bug because: 



Currently the CVO marks an upgrade as failed whenever an operator takes longer than 20 minutes to rollout. It's very common on clusters of any size to take more than 20 minutes to rollout operators which have daemonsets running on all hosts, in particular MCO, network, and dns operators. By moving this to 40 minutes we'll significantly reduce the noise so we can focus on upgrades which have real problems.

There's follow up to make more significant implementation changes here but we'll push those out more slowly

https://issues.redhat.com/browse/OTA-247
Comment 1 W. Trevor King 2020-10-04 02:28:20 UTC 
Waiting on QE to verify the 4.6 bug.
Comment 2 W. Trevor King 2020-10-25 15:55:50 UTC 
Bug 1884334 is now blocking on a refactor, so closing this for now.  We'll revisit backports once we have a complete fix.
Note You need to log in before you can comment on or make changes to this bug.