Bug 1763772 - SyncingFailed and other waitForDeploymentRollout consumers often show only 'timed out waiting for the condition'
Summary: SyncingFailed and other waitForDeploymentRollout consumers often show only 't...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute
Version: 4.1.z
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.1.z
Assignee: W. Trevor King
QA Contact: Jianwei Hou
URL:
Whiteboard:
Depends On: 1763293
Blocks: 1763295
TreeView+ depends on / blocked
 
Reported: 2019-10-21 15:00 UTC by W. Trevor King
Modified: 2020-01-20 18:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1763293
Environment:
Last Closed: 2020-01-20 18:16:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description W. Trevor King 2019-10-21 15:00:41 UTC
+++ This bug was initially created as a clone of Bug #1763293 +++

We currently get errors like [1]:

  Oct 17 18:41:52.205 E clusteroperator/machine-api changed Degraded to True: SyncingFailed: Failed when progressing towards operator: 4.3.0-0.ci-2019-10-17-173803 because timed out waiting for the condition

But "timed out waiting for the condition" is not as useful as whatever it was that made us decide the last poll wasn't good enough.  We should put that reason in the message instead.

[1]: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade/8809


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