Bug 1703140

Summary: Unexpected error occurred: Cluster did not acknowledge request to upgrade in a reasonable time
Product: OpenShift Container Platform Reporter: bpeterse
Component: Cluster Version OperatorAssignee: Abhinav Dahiya <adahiya>
Status: CLOSED DUPLICATE QA Contact: liujia <jiajliu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: aos-bugs, bleanhar, jokerman, mmccomas
Target Milestone: ---   
Target Release: 4.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-04-25 17:34:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***