Bug 1703140 - Unexpected error occurred: Cluster did not acknowledge request to upgrade in a reasonable time
Summary: Unexpected error occurred: Cluster did not acknowledge request to upgrade in ...
Keywords:
Status: CLOSED DUPLICATE of bug 1703158
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 4.1.0
Assignee: Abhinav Dahiya
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-25 15:38 UTC by bpeterse
Modified: 2019-04-25 17:34 UTC (History)
4 users (show)

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


Attachments (Terms of Use)

Description bpeterse 2019-04-25 15:38:53 UTC
Description of problem:

5% of failures since the start of my build-cop rotation report:

```
  Unexpected error occurred: Cluster did not acknowledge request to upgrade in a reasonable time: timed out waiting for the condition
```

This is semi-helpful, but there is still some unknown condition in this error message that makes it difficult to know what exactly when wrong and how to fix. 

Additional information errors:

```
Expected error:
<*errors.errorString | 0xc42068d700>: {
s: "Cluster did not acknowledge request to upgrade in a reasonable time: timed out waiting for the condition",
}
Cluster did not acknowledge request to upgrade in a reasonable time: timed out waiting for the condition
not to have occurred
```  
"expected error 'timed out waiting for the condition not to have occurred'" is difficult to debug.

Comment 1 bpeterse 2019-04-25 15:40:09 UTC
This is more or less an "improve the error message if possible" bug.

Comment 2 Brenton Leanhardt 2019-04-25 17:34:09 UTC

*** This bug has been marked as a duplicate of bug 1703158 ***


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