Job:
periodic-ci-openshift-release-master-nightly-4.17-e2e-metal-ovn-single-node-rt-upgrade-serial (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1846243306892169216junit6 hours ago
# [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:187]: during upgrade to registry.build10.ci.openshift.org/ci-op-wx5gflsb/release@sha256:a14f662812ceaaaf6bcae1bdef17cb4a1cfb1a2e8418b83e4061a773f1a9d364: Timed out waiting for cluster to acknowledge upgrade: timed out waiting for the condition; observedGeneration: 2; updated.Generation: 3
Ginkgo exit error 1: exit with code 1
periodic-ci-openshift-release-master-nightly-4.18-e2e-metal-ovn-single-node-rt-upgrade-serial (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1846243306967666688junit6 hours ago
# [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:187]: during upgrade to registry.build10.ci.openshift.org/ci-op-idlw1204/release@sha256:a697cb3f0afbb26f71672ef69223701f741f9c0de9ee90107fe9dbfc8782fc34: Timed out waiting for cluster to acknowledge upgrade: timed out waiting for the condition; observedGeneration: 2; updated.Generation: 3
Ginkgo exit error 1: exit with code 1
rehearse-56884-periodic-ci-openshift-release-master-nightly-4.18-upgrade-from-stable-4.17-e2e-metal-ovn-single-node-rt-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact
#1846162420855214080junit11 hours ago
# [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:187]: during upgrade to registry.build10.ci.openshift.org/ci-op-7yxrt2f4/release@sha256:a697cb3f0afbb26f71672ef69223701f741f9c0de9ee90107fe9dbfc8782fc34: Timed out waiting for cluster to acknowledge upgrade: timed out waiting for the condition; observedGeneration: 2; updated.Generation: 3
Ginkgo exit error 1: exit with code 1
periodic-ci-openshift-release-master-nightly-4.17-e2e-metal-ipi-upgrade-ovn-ipv6 (all) - 8 runs, 13% failed, 100% of failures match = 13% impact
#1845963774171811840junit24 hours ago
# [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:187]: during upgrade to registry.build05.ci.openshift.org/ci-op-rdq0yp10/release@sha256:303d9b854ec4dee473f9191f8368b67c4c739e66a40bf8691ceed47e338affca: Timed out waiting for cluster to acknowledge upgrade: timed out waiting for the condition; observedGeneration: 2; updated.Generation: 3
Ginkgo exit error 1: exit with code 1
periodic-ci-openshift-release-master-nightly-4.17-upgrade-from-stable-4.16-e2e-metal-ipi-upgrade-ovn-ipv6 (all) - 7 runs, 14% failed, 100% of failures match = 14% impact
#1845963754878013440junit24 hours ago
# [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:187]: during upgrade to registry.build05.ci.openshift.org/ci-op-9nfitpz8/release@sha256:303d9b854ec4dee473f9191f8368b67c4c739e66a40bf8691ceed47e338affca: Timed out waiting for cluster to acknowledge upgrade: timed out waiting for the condition; observedGeneration: 2; updated.Generation: 3
Ginkgo exit error 1: exit with code 1
periodic-ci-openshift-release-master-nightly-4.15-e2e-metal-ipi-upgrade-ovn-ipv6 (all) - 7 runs, 29% failed, 50% of failures match = 14% impact
#1845765981054439424junit37 hours ago
# [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]
fail [github.com/openshift/origin/test/e2e/upgrade/upgrade.go:186]: during upgrade to registry.build05.ci.openshift.org/ci-op-l57db7c8/release@sha256:99a41ef75cb5d1fc6d075957f164deb076dd6201ef4a4414c0bc9f8ae277e601: Timed out waiting for cluster to acknowledge upgrade: timed out waiting for the condition; observedGeneration: 2; updated.Generation: 3
Ginkgo exit error 1: exit with code 1

Found in 0.01% of runs (0.09% of failures) across 42606 total runs and 6657 jobs (16.23% failed) in 1.269s - clear search | chart view - source code located on github