test: [sig-cluster-lifecycle] Cluster completes upgrade is failing frequently in CI, see search results: https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cluster-lifecycle%5C%5D+Cluster+completes+upgrade https://prow.ci.openshift.org/view/gs/origin-ci-test/logs/release-openshift-origin-installer-e2e-aws-upgrade-4.5-stable-to-4.6-ci/1298224662781628416 ---------------------- [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial] [Suite:openshift] expand_less 2h37m26s fail [github.com/openshift/origin@/test/e2e/upgrade/upgrade.go:139]: during upgrade to registry.svc.ci.openshift.org/ocp/release:4.6.0-0.ci-2020-08-24-152549 Unexpected error: <*errors.errorString | 0xc001e7e5a0>: { s: "Cluster did not complete upgrade: timed out waiting for the condition: Cluster operator ingress is reporting a failure: Some ingresscontrollers are degraded: default", } Cluster did not complete upgrade: timed out waiting for the condition: Cluster operator ingress is reporting a failure: Some ingresscontrollers are degraded: default occurred
"Some ingresscontrollers are degraded: default" doesn't point the finger clearly at a different component, so assigning to the ingress folks.
Target set to 4.7 while investigation is either ongoing or not yet started. Will be considered for earlier release versions when diagnosed and resolved.
Pulling back to 4.6 to pick up the in-flight fix.
checked https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cluster-lifecycle%5C%5D+Cluster+completes+upgrade and didn't see the issue again.
@build-watcher: this has a couple failures in 4.7 in the past couple days, are they worth visiting? See https://search.ci.openshift.org/?maxAge=168h&context=1&type=bug%2Bjunit&name=4.7&maxMatches=5&maxBytes=20971520&groupBy=job&search=%5C%5Bsig-cluster-lifecycle%5C%5D+Cluster+completes+upgrade
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196