| periodic-ci-openshift-release-master-ci-4.9-upgrade-from-stable-4.8-e2e-gcp-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1666426090882600960 | junit | 26 hours ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption (AWS has a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1943804) for at least 1s of 1h19m17s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-aws-ovn-upgrade (all) - 2 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1665933248301109248 | junit | 2 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption for at least 2s of 1h7m53s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| #1665843157633339392 | junit | 2 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption for at least 6s of 1h13m36s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-ci-4.7-e2e-gcp-upgrade (all) - 2 runs, 0% failed, 100% of runs match | |||
| #1665843157511704576 | junit | 2 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption for at least 6s of 1h7m29s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| #1665776463313375232 | junit | 2 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption for at least 4s of 1h7m45s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-gcp-upgrade (all) - 2 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1665734742068170752 | junit | 3 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption (AWS has a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1943804) for at least 11s of 1h20m53s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| #1665659225310760960 | junit | 3 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption (AWS has a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1943804) for at least 0s of 1h20m35s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-vsphere-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1665667112900759552 | junit | 3 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption (AWS has a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1943804) for at least 13s of 1h24m23s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-ci-4.7-e2e-aws-upgrade-rollback (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1665471050843951104 | junit | 3 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption for at least 2s of 1h7m55s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-nightly-4.9-upgrade-from-stable-4.8-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1665405619026268160 | junit | 3 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption (AWS has a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1943804) for at least 2m28s of 2h32m23s (2%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-ci-4.8-e2e-aws-upgrade-ovn-single-node (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1665312755915165696 | junit | 4 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections Jun 4 14:16:11.442: API "kubernetes-api-available-new-connections" was unreachable during disruption (AWS has a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1943804) for at least 2m35s of 2h32m21s (2%): | |||
| periodic-ci-openshift-release-master-ci-4.7-upgrade-from-stable-4.6-e2e-gcp-upgrade (all) - 1 runs, 0% failed, 100% of runs match | |||
| #1664946085581295616 | junit | 5 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption for at least 5s of 1h20m16s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
| periodic-ci-openshift-release-master-ci-4.8-upgrade-from-stable-4.7-e2e-gcp-ovn-upgrade (all) - 1 runs, 100% failed, 100% of failures match = 100% impact | |||
| #1664550050195312640 | junit | 6 days ago | |
# [sig-api-machinery] Kubernetes APIs remain available for new connections API "kubernetes-api-available-new-connections" was unreachable during disruption (AWS has a known issue: https://bugzilla.redhat.com/show_bug.cgi?id=1943804) for at least 0s of 1h24m50s (0%), this is currently sufficient to pass the test/job but not considered completely correct: | |||
Found in 0.01% of runs (0.05% of failures) across 132592 total runs and 7693 jobs (18.33% failed) in 1.343s - clear search | chart view - source code located on github