Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1754526

Summary: [build-cop] [Disruptive] Cluster upgrade should maintain a functioning cluster [Feature:ClusterUpgrade] [Suite:openshift] [Serial]
Product: OpenShift Container Platform Reporter: Lokesh Mandvekar <lsm5>
Component: Machine Config OperatorAssignee: Antonio Murdaca <amurdaca>
Status: CLOSED DUPLICATE QA Contact: Michael Nguyen <mnguyen>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: mpatel, trankin, walters
Target Milestone: ---   
Target Release: ---   
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-09-23 17:26:46 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:
Bug Depends On:    
Bug Blocks: 1754523, 1755066    

Description Lokesh Mandvekar 2019-09-23 13:33:08 UTC
Description of problem:

fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:139]: during upgrade
Unexpected error:
    <*errors.errorString | 0xc002160b60>: {
        s: "Cluster did not complete upgrade: timed out waiting for the condition: unable to retrieve cluster version during upgrade: the server could not find the requested resource (get clusterversions.config.openshift.io version)",
    }
    Cluster did not complete upgrade: timed out waiting for the condition: unable to retrieve cluster version during upgrade: the server could not find the requested resource (get clusterversions.config.openshift.io version)
occurred

Comment 1 Colin Walters 2019-09-23 17:12:39 UTC
Not enough information here; which job was this?  Ideally buildcops do a bit of basic triage like "is this happening 100% of the time" or "saw this once".

Moving back to unspecified by default until someone determines this should be a 4.2 blocker.

Comment 2 Lokesh Mandvekar 2019-09-23 17:22:42 UTC
Err, sorry, it's at https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.1-to-4.2/176 . So far, only seen this once. A similar one (but not quite the same) mentioned on Friday's report, https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-rollback-4.1-to-4.2/170 where it mentioned a connection refused error.

Comment 3 Mrunal Patel 2019-09-23 17:26:46 UTC

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