Skip to content

NO-ISSUE: Automated - Update synthetic test data - #31581

Merged
dgoodwin merged 1 commit into
mainfrom
no-issue--automated---update-synthetic-test-data
Sep 1, 2026
Merged

NO-ISSUE: Automated - Update synthetic test data#31581
dgoodwin merged 1 commit into
mainfrom
no-issue--automated---update-synthetic-test-data

Conversation

@openshift-ci

@openshift-ci openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

disruptions Information

There were (3938) added jobs and (232) were removed.

Comparisons were above allowed leeway of 30.00%

Note: For P99, disruptions had 483 jobs increased and 1123 jobs decreased.

Click To Show Table
Name Release From Arch Network Platform Topology Job Results P95 P95 % Increase P99 P99 % Increase
pod-to-host-new-connections 5.0 4.22 amd64 ovn gcp ha 530 35.55s 788.75% 1m25s 65.79%
pod-to-host-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 35s 600.00% 1m24.71s 69.42%
host-to-host-new-connections 5.0 4.22 amd64 ovn azure ha 868 38s 90.00% 58.32s 68.85%
host-to-host-new-connections 5.0 4.22 amd64 ovn gcp ha 530 28s 115.38% 41.13s 85.44%
host-to-host-new-connections 5.0 amd64 ovn azure ha 231 18s 200.00% 34.4s 233.33%
host-to-host-reused-connections 5.0 4.22 amd64 ovn azure ha 868 14.65s 144.17% 30.66s 155.50%
openshift-api-http2-internal-lb-reused-connections 5.0 amd64 ovn gcp ha 208 8.3s 730.00% 18.93s 531.00%
host-to-host-new-connections 5.0 5.0 amd64 ovn gcp ha 757 13s 116.67% 19.44s 94.40%
host-to-host-new-connections 5.0 4.22 amd64 ovn aws ha 906 7s 250.00% 11.91s 138.20%
kube-api-http2-internal-lb-new-connections 5.0 amd64 ovn aws external 583 6s 361.54% 28.18s 1415.05%
host-to-host-new-connections 5.0 amd64 ovn aws external 584 5s 1566.67% 8.17s 850.00%
openshift-api-http2-internal-lb-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 15s 43.54% 24.55s 44.41%
host-to-host-new-connections 5.0 amd64 ovn azure external 637 10s 66.67% 14s 65.48%
openshift-api-http2-internal-lb-new-connections 5.0 amd64 ovn aws external 583 6s 200.00% 31s 675.00%
openshift-api-http2-service-network-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 14s 33.97% 24.13s 33.39%
openshift-api-http2-service-network-new-connections 5.0 amd64 ovn aws external 583 10.9s 36.25% 23.18s 44.88%
metrics-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 3.55s 255.00% 1m26.68s 1323.32%
kube-api-http1-internal-lb-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 5s 66.67%
kube-api-http2-internal-lb-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 5s 66.67%
kube-api-http1-internal-lb-new-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 6.71s 111.01%
kube-api-http2-internal-lb-new-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 7s 120.13%
metrics-api-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 2s 100.00% 5s 66.67%
kube-api-http1-internal-lb-new-connections 5.0 arm64 ovn aws ha 165 2s 100.00% 4.08s 104.00%
kube-api-http2-service-network-new-connections 5.0 amd64 ovn azure ha 231 4s 33.33% 5s 63.40%
kube-api-http2-internal-lb-new-connections 5.0 arm64 ovn aws ha 165 2s 100.00% 6.24s 212.00%
kube-api-new-connections 5.0 amd64 ovn gcp ha 312 1s 900.00% 16.89s 1589.00%
metrics-api-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 185.71% 3s 32.16%
openshift-api-http2-internal-lb-new-connections 5.0 arm64 ovn aws ha 182 1s 150.00% 3s 200.00%
openshift-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m8s 125.47%
openshift-api-reused-connections 5.0 amd64 ovn aws external 585 0s 0.00% 11.16s 1016.00%
kube-api-http1-service-network-reused-connections 5.0 amd64 ovn gcp ha 208 0s 0.00% 1.93s 359.52%
openshift-api-http2-localhost-new-connections 5.0 amd64 ovn gcp ha 312 1m33s 0.00% 1m37.78s 9678.00%
metrics-api-reused-connections 5.0 amd64 ovn azure ha 115 1s 0.00% 2.72s 36.00%
openshift-api-reused-connections 5.0 amd64 ovn azure ha 115 1s 0.00% 2.86s 50.53%
kube-api-http1-localhost-new-connections 5.0 amd64 ovn azure ha 231 1m13s 0.00% 3m18.7s 154.45%
cache-kube-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
kube-api-http2-localhost-new-connections 5.0 amd64 ovn gcp ha 312 1m15.45s 0.00% 1m20.89s 20122.50%
openshift-api-http2-internal-lb-new-connections 5.0 multi ovn aws ha 150 1s 0.00% 2s 100.00%
ingress-to-console-new-connections 5.0 amd64 ovn vsphere ha 627 4s 0.00% 6s 574.16%
kube-api-http1-internal-lb-new-connections 5.0 5.0 amd64 ovn azure ha 572 1s 0.00% 2s 100.00%
cache-openshift-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m29.42s 706.31%
image-registry-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 2s 100.00%
ingress-to-oauth-server-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 0.00% 3s 32.16%
metrics-api-reused-connections 5.0 4.22 amd64 ovn azure ha 868 2s 0.00% 4s 33.33%
kube-api-http2-internal-lb-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 360ms 176.92%
pod-to-pod-new-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14s 1002.36%
kube-api-http2-internal-lb-new-connections 5.0 multi ovn aws ha 150 1s 0.00% 2s 100.00%
service-load-balancer-with-pdb-new-connections 5.0 amd64 ovn gcp ha 206 750ms 0.00% 4.95s 395.00%
cache-openshift-api-new-connections 5.0 ppc64le ovn none ha 151 6.5s 0.00% 2m3.5s 124.55%
aws-network-liveness-new-connections 5.0 5.0 amd64 ovn aws single 518 0s 0.00% 3.83s 91.50%
ingress-to-console-reused-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 2s 100.00%
service-load-balancer-with-pdb-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 0.00% 3s 50.00%
kube-api-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 3.16s 58.00%
cache-openshift-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
cache-oauth-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m29.23s 166.92%
cache-openshift-api-reused-connections 5.0 amd64 ovn azure ha 112 1s 0.00% 2s 100.00%
host-to-host-new-connections 5.0 arm64 ovn aws ha 165 800ms 0.00% 55.48s 2504.69%
kube-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m20.81s 611.36%
oauth-api-new-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 6.24s 300.00%
openshift-api-reused-connections 5.0 arm64 ovn aws ha 182 0s 0.00% 1s 669.23%
cache-oauth-api-reused-connections 5.0 amd64 ovn azure ha 115 1s 0.00% 1.86s 86.00%
oauth-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m25.13s 54.03%
ingress-to-console-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 360ms 176.92%
host-to-pod-new-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14.66s 1054.33%
host-to-host-reused-connections 5.0 amd64 ovn azure external 637 1s 0.00% 4s 300.00%
service-load-balancer-with-pdb-new-connections 5.0 5.0 amd64 ovn azure ha 572 0s 0.00% 3.29s 229.00%
openshift-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m33.68s 520.81%
kube-api-new-connections 5.0 amd64 ovn azure ha 231 0s 0.00% 700ms 2233.33%
cache-openshift-api-reused-connections 5.0 amd64 ovn metal ha 116 0s 0.00% 1s 33.33%
kube-api-http1-internal-lb-new-connections 5.0 multi ovn aws ha 150 1s 0.00% 2s 100.00%
openshift-api-http2-localhost-reused-connections 5.0 amd64 ovn azure ha 231 1m20.5s 0.00% 3m51.5s 186.16%
azure-network-liveness-new-connections 5.0 5.0 amd64 ovn aws ha 661 0s 0.00% 2.4s 87.50%
cache-kube-api-new-connections 5.0 amd64 ovn gcp ha 208 650ms 0.00% 1.93s 93.00%
kube-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
cache-kube-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m28.71s 706.45%
kube-api-http2-service-network-new-connections 5.0 amd64 ovn aws external 583 9s 0.00% 24.18s 42.24%
pod-to-service-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 0.00% 1.33s 33.00%
pod-to-host-new-connections 5.0 amd64 ovn azure ha 115 0s 0.00% 1.72s 421.21%
ingress-to-console-new-connections 5.0 amd64 ovn gcp ha 208 0s 0.00% 1s 1566.67%
ci-cluster-network-liveness-new-connections 5.0 arm64 ovn aws ha 165 2s 0.00% 34.56s 2316.78%
host-to-host-new-connections 5.0 multi ovn aws ha 150 2s 0.00% 5s 114.59%
ingress-to-oauth-server-new-connections 5.0 5.0 amd64 ovn azure ha 572 0s 0.00% 2s 108.33%
metrics-api-new-connections 5.0 arm64 ovn aws ha 182 0s 0.00% 380ms 46.15%
cache-oauth-api-new-connections 5.0 amd64 ovn gcp ha 208 1s 0.00% 2s 100.00%
kube-api-reused-connections 5.0 amd64 ovn gcp ha 208 0s 0.00% 1s 1566.67%
host-to-host-new-connections 5.0 5.0 amd64 ovn azure ha 572 10s 0.00% 33.58s 52.64%
cache-openshift-api-new-connections 5.0 amd64 ovn gcp ha 312 1s 0.00% 18.78s 1778.00%
host-to-host-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 4s 0.00% 9s 191.26%
openshift-api-http2-internal-lb-new-connections 5.0 amd64 ovn azure ha 207 2s 0.00% 3s 9900.00%
pod-to-pod-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 0s 0.00% 2s 100.00%
pod-to-pod-reused-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14s 1300.00%
ci-cluster-network-liveness-new-connections 5.0 amd64 ovn azure external 640 0s 0.00% 3.61s 80.50%
oauth-api-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 3.88s 288.00%
kube-api-http2-service-network-reused-connections 5.0 amd64 ovn gcp ha 312 1s 0.00% 1.89s 89.00%
host-to-pod-reused-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14.66s 1366.00%
ci-cluster-network-liveness-new-connections 5.0 4.22 amd64 ovn gcp ha 530 22.05s 0.00% 1m52.55s 85.91%
pod-to-pod-new-connections 5.0 4.22 amd64 ovn gcp ha 530 0s 0.00% 1.71s 71.00%
cache-oauth-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
kube-api-new-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 2.44s 93.65%
cache-kube-api-reused-connections 5.0 amd64 ovn metal ha 148 0s 0.00% 5.83s 4064.29%

alerts Information

There were (35082) added jobs and (7826) were removed.

Comparisons were above allowed leeway of 30.00%

Note: For P99, alerts had 36 jobs increased and 527 jobs decreased.

Click To Show Table
Name Release From Arch Network Platform Topology Job Results P95 P95 % Increase P99 P99 % Increase
KubeJobFailed openshift-insights Warning 5.0 amd64 ovn gcp ha 145 2h55m26.8s 55.99% 8h1m59.52s 57.81%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 amd64 ovn vsphere ha 239 1h35m48.8s 73.50% 2h49m35.44s 138.52%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 4.22 amd64 ovn aws ha 133 30m15.2s 95.18% 36m54.96s 53.64%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 amd64 ovn metal ha 246 43m38s 31.56% 1h3m39.7s 56.09%
HighOverallControlPlaneCPU openshift-kube-apiserver Warning 5.0 amd64 ovn vsphere ha 239 8m34s 247.30% 32m29s 172.59%
HighOverallControlPlaneCPU openshift-kube-apiserver Warning 5.0 amd64 ovn aws ha 441 4m26s 49.44% 16m14s 267.13%
KubeJobFailed openshift-insights Warning 5.0 4.22 amd64 ovn aws ha 133 1h55m20.4s 0.00% 3h32m52.32s 94.41%
NodeSystemSaturation openshift-monitoring Warning 5.0 amd64 ovn aws ha 441 28s 0.00% 9m44.8s 105.55%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 5.0 amd64 ovn gcp ha 188 39m38.4s 0.00% 44m41.04s 187.81%
TestAlertFeatureE2ETestOTA1813 openshift-cluster-version Critical 5.0 amd64 ovn gcp ha 145 1m1.6s 0.00% 2m6s 65.79%
TestAlertFeatureE2ETestOTA1813 openshift-cluster-version Critical 5.0 amd64 ovn metal ha 246 33s 0.00% 1m53.3s 49.08%
TestAlertFeatureE2ETestOTA1813 openshift-cluster-version Critical 5.0 amd64 ovn aws ha 441 1m8s 0.00% 1m50.4s 31.71%
HighOverallControlPlaneCPU openshift-kube-apiserver Warning 5.0 amd64 ovn metal two-node-fencing 253 0s 0.00% 58s 431.14%
/cc @xueqzhan, @neisw, @smg247

@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Sep 1, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@openshift-ci[bot]: This pull request explicitly references no jira issue.

Details

In response to this:

disruptions Information

There were (3938) added jobs and (232) were removed.

Comparisons were above allowed leeway of 30.00%

Note: For P99, disruptions had 483 jobs increased and 1123 jobs decreased.

Click To Show Table
Name Release From Arch Network Platform Topology Job Results P95 P95 % Increase P99 P99 % Increase
pod-to-host-new-connections 5.0 4.22 amd64 ovn gcp ha 530 35.55s 788.75% 1m25s 65.79%
pod-to-host-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 35s 600.00% 1m24.71s 69.42%
host-to-host-new-connections 5.0 4.22 amd64 ovn azure ha 868 38s 90.00% 58.32s 68.85%
host-to-host-new-connections 5.0 4.22 amd64 ovn gcp ha 530 28s 115.38% 41.13s 85.44%
host-to-host-new-connections 5.0 amd64 ovn azure ha 231 18s 200.00% 34.4s 233.33%
host-to-host-reused-connections 5.0 4.22 amd64 ovn azure ha 868 14.65s 144.17% 30.66s 155.50%
openshift-api-http2-internal-lb-reused-connections 5.0 amd64 ovn gcp ha 208 8.3s 730.00% 18.93s 531.00%
host-to-host-new-connections 5.0 5.0 amd64 ovn gcp ha 757 13s 116.67% 19.44s 94.40%
host-to-host-new-connections 5.0 4.22 amd64 ovn aws ha 906 7s 250.00% 11.91s 138.20%
kube-api-http2-internal-lb-new-connections 5.0 amd64 ovn aws external 583 6s 361.54% 28.18s 1415.05%
host-to-host-new-connections 5.0 amd64 ovn aws external 584 5s 1566.67% 8.17s 850.00%
openshift-api-http2-internal-lb-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 15s 43.54% 24.55s 44.41%
host-to-host-new-connections 5.0 amd64 ovn azure external 637 10s 66.67% 14s 65.48%
openshift-api-http2-internal-lb-new-connections 5.0 amd64 ovn aws external 583 6s 200.00% 31s 675.00%
openshift-api-http2-service-network-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 14s 33.97% 24.13s 33.39%
openshift-api-http2-service-network-new-connections 5.0 amd64 ovn aws external 583 10.9s 36.25% 23.18s 44.88%
metrics-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 3.55s 255.00% 1m26.68s 1323.32%
kube-api-http1-internal-lb-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 5s 66.67%
kube-api-http2-internal-lb-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 5s 66.67%
kube-api-http1-internal-lb-new-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 6.71s 111.01%
kube-api-http2-internal-lb-new-connections 5.0 4.22 amd64 ovn gcp ha 530 3s 200.00% 7s 120.13%
metrics-api-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 2s 100.00% 5s 66.67%
kube-api-http1-internal-lb-new-connections 5.0 arm64 ovn aws ha 165 2s 100.00% 4.08s 104.00%
kube-api-http2-service-network-new-connections 5.0 amd64 ovn azure ha 231 4s 33.33% 5s 63.40%
kube-api-http2-internal-lb-new-connections 5.0 arm64 ovn aws ha 165 2s 100.00% 6.24s 212.00%
kube-api-new-connections 5.0 amd64 ovn gcp ha 312 1s 900.00% 16.89s 1589.00%
metrics-api-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 185.71% 3s 32.16%
openshift-api-http2-internal-lb-new-connections 5.0 arm64 ovn aws ha 182 1s 150.00% 3s 200.00%
openshift-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m8s 125.47%
openshift-api-reused-connections 5.0 amd64 ovn aws external 585 0s 0.00% 11.16s 1016.00%
kube-api-http1-service-network-reused-connections 5.0 amd64 ovn gcp ha 208 0s 0.00% 1.93s 359.52%
openshift-api-http2-localhost-new-connections 5.0 amd64 ovn gcp ha 312 1m33s 0.00% 1m37.78s 9678.00%
metrics-api-reused-connections 5.0 amd64 ovn azure ha 115 1s 0.00% 2.72s 36.00%
openshift-api-reused-connections 5.0 amd64 ovn azure ha 115 1s 0.00% 2.86s 50.53%
kube-api-http1-localhost-new-connections 5.0 amd64 ovn azure ha 231 1m13s 0.00% 3m18.7s 154.45%
cache-kube-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
kube-api-http2-localhost-new-connections 5.0 amd64 ovn gcp ha 312 1m15.45s 0.00% 1m20.89s 20122.50%
openshift-api-http2-internal-lb-new-connections 5.0 multi ovn aws ha 150 1s 0.00% 2s 100.00%
ingress-to-console-new-connections 5.0 amd64 ovn vsphere ha 627 4s 0.00% 6s 574.16%
kube-api-http1-internal-lb-new-connections 5.0 5.0 amd64 ovn azure ha 572 1s 0.00% 2s 100.00%
cache-openshift-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m29.42s 706.31%
image-registry-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 2s 100.00%
ingress-to-oauth-server-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 0.00% 3s 32.16%
metrics-api-reused-connections 5.0 4.22 amd64 ovn azure ha 868 2s 0.00% 4s 33.33%
kube-api-http2-internal-lb-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 360ms 176.92%
pod-to-pod-new-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14s 1002.36%
kube-api-http2-internal-lb-new-connections 5.0 multi ovn aws ha 150 1s 0.00% 2s 100.00%
service-load-balancer-with-pdb-new-connections 5.0 amd64 ovn gcp ha 206 750ms 0.00% 4.95s 395.00%
cache-openshift-api-new-connections 5.0 ppc64le ovn none ha 151 6.5s 0.00% 2m3.5s 124.55%
aws-network-liveness-new-connections 5.0 5.0 amd64 ovn aws single 518 0s 0.00% 3.83s 91.50%
ingress-to-console-reused-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 2s 100.00%
service-load-balancer-with-pdb-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 0.00% 3s 50.00%
kube-api-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 3.16s 58.00%
cache-openshift-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
cache-oauth-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m29.23s 166.92%
cache-openshift-api-reused-connections 5.0 amd64 ovn azure ha 112 1s 0.00% 2s 100.00%
host-to-host-new-connections 5.0 arm64 ovn aws ha 165 800ms 0.00% 55.48s 2504.69%
kube-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m20.81s 611.36%
oauth-api-new-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 6.24s 300.00%
openshift-api-reused-connections 5.0 arm64 ovn aws ha 182 0s 0.00% 1s 669.23%
cache-oauth-api-reused-connections 5.0 amd64 ovn azure ha 115 1s 0.00% 1.86s 86.00%
oauth-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m25.13s 54.03%
ingress-to-console-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 360ms 176.92%
host-to-pod-new-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14.66s 1054.33%
host-to-host-reused-connections 5.0 amd64 ovn azure external 637 1s 0.00% 4s 300.00%
service-load-balancer-with-pdb-new-connections 5.0 5.0 amd64 ovn azure ha 572 0s 0.00% 3.29s 229.00%
openshift-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m33.68s 520.81%
kube-api-new-connections 5.0 amd64 ovn azure ha 231 0s 0.00% 700ms 2233.33%
cache-openshift-api-reused-connections 5.0 amd64 ovn metal ha 116 0s 0.00% 1s 33.33%
kube-api-http1-internal-lb-new-connections 5.0 multi ovn aws ha 150 1s 0.00% 2s 100.00%
openshift-api-http2-localhost-reused-connections 5.0 amd64 ovn azure ha 231 1m20.5s 0.00% 3m51.5s 186.16%
azure-network-liveness-new-connections 5.0 5.0 amd64 ovn aws ha 661 0s 0.00% 2.4s 87.50%
cache-kube-api-new-connections 5.0 amd64 ovn gcp ha 208 650ms 0.00% 1.93s 93.00%
kube-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
cache-kube-api-new-connections 5.0 4.22 amd64 ovn gcp ha 530 1s 0.00% 1m28.71s 706.45%
kube-api-http2-service-network-new-connections 5.0 amd64 ovn aws external 583 9s 0.00% 24.18s 42.24%
pod-to-service-new-connections 5.0 4.22 amd64 ovn azure ha 868 1s 0.00% 1.33s 33.00%
pod-to-host-new-connections 5.0 amd64 ovn azure ha 115 0s 0.00% 1.72s 421.21%
ingress-to-console-new-connections 5.0 amd64 ovn gcp ha 208 0s 0.00% 1s 1566.67%
ci-cluster-network-liveness-new-connections 5.0 arm64 ovn aws ha 165 2s 0.00% 34.56s 2316.78%
host-to-host-new-connections 5.0 multi ovn aws ha 150 2s 0.00% 5s 114.59%
ingress-to-oauth-server-new-connections 5.0 5.0 amd64 ovn azure ha 572 0s 0.00% 2s 108.33%
metrics-api-new-connections 5.0 arm64 ovn aws ha 182 0s 0.00% 380ms 46.15%
cache-oauth-api-new-connections 5.0 amd64 ovn gcp ha 208 1s 0.00% 2s 100.00%
kube-api-reused-connections 5.0 amd64 ovn gcp ha 208 0s 0.00% 1s 1566.67%
host-to-host-new-connections 5.0 5.0 amd64 ovn azure ha 572 10s 0.00% 33.58s 52.64%
cache-openshift-api-new-connections 5.0 amd64 ovn gcp ha 312 1s 0.00% 18.78s 1778.00%
host-to-host-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 4s 0.00% 9s 191.26%
openshift-api-http2-internal-lb-new-connections 5.0 amd64 ovn azure ha 207 2s 0.00% 3s 9900.00%
pod-to-pod-reused-connections 5.0 4.22 amd64 ovn gcp ha 530 0s 0.00% 2s 100.00%
pod-to-pod-reused-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14s 1300.00%
ci-cluster-network-liveness-new-connections 5.0 amd64 ovn azure external 640 0s 0.00% 3.61s 80.50%
oauth-api-reused-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 3.88s 288.00%
kube-api-http2-service-network-reused-connections 5.0 amd64 ovn gcp ha 312 1s 0.00% 1.89s 89.00%
host-to-pod-reused-connections 5.0 4.22 amd64 ovn azure ha 868 0s 0.00% 14.66s 1366.00%
ci-cluster-network-liveness-new-connections 5.0 4.22 amd64 ovn gcp ha 530 22.05s 0.00% 1m52.55s 85.91%
pod-to-pod-new-connections 5.0 4.22 amd64 ovn gcp ha 530 0s 0.00% 1.71s 71.00%
cache-oauth-api-new-connections 5.0 s390x ovn none ha 163 0s 0.00% 2m7.38s 124.38%
kube-api-new-connections 5.0 arm64 ovn aws ha 165 0s 0.00% 2.44s 93.65%
cache-kube-api-reused-connections 5.0 amd64 ovn metal ha 148 0s 0.00% 5.83s 4064.29%

alerts Information

There were (35082) added jobs and (7826) were removed.

Comparisons were above allowed leeway of 30.00%

Note: For P99, alerts had 36 jobs increased and 527 jobs decreased.

Click To Show Table
Name Release From Arch Network Platform Topology Job Results P95 P95 % Increase P99 P99 % Increase
KubeJobFailed openshift-insights Warning 5.0 amd64 ovn gcp ha 145 2h55m26.8s 55.99% 8h1m59.52s 57.81%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 amd64 ovn vsphere ha 239 1h35m48.8s 73.50% 2h49m35.44s 138.52%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 4.22 amd64 ovn aws ha 133 30m15.2s 95.18% 36m54.96s 53.64%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 amd64 ovn metal ha 246 43m38s 31.56% 1h3m39.7s 56.09%
HighOverallControlPlaneCPU openshift-kube-apiserver Warning 5.0 amd64 ovn vsphere ha 239 8m34s 247.30% 32m29s 172.59%
HighOverallControlPlaneCPU openshift-kube-apiserver Warning 5.0 amd64 ovn aws ha 441 4m26s 49.44% 16m14s 267.13%
KubeJobFailed openshift-insights Warning 5.0 4.22 amd64 ovn aws ha 133 1h55m20.4s 0.00% 3h32m52.32s 94.41%
NodeSystemSaturation openshift-monitoring Warning 5.0 amd64 ovn aws ha 441 28s 0.00% 9m44.8s 105.55%
HighOverallControlPlaneMemory openshift-machine-config-operator Warning 5.0 5.0 amd64 ovn gcp ha 188 39m38.4s 0.00% 44m41.04s 187.81%
TestAlertFeatureE2ETestOTA1813 openshift-cluster-version Critical 5.0 amd64 ovn gcp ha 145 1m1.6s 0.00% 2m6s 65.79%
TestAlertFeatureE2ETestOTA1813 openshift-cluster-version Critical 5.0 amd64 ovn metal ha 246 33s 0.00% 1m53.3s 49.08%
TestAlertFeatureE2ETestOTA1813 openshift-cluster-version Critical 5.0 amd64 ovn aws ha 441 1m8s 0.00% 1m50.4s 31.71%
HighOverallControlPlaneCPU openshift-kube-apiserver Warning 5.0 amd64 ovn metal two-node-fencing 253 0s 0.00% 58s 431.14%
/cc @xueqzhan, @neisw, @smg247

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot added the ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review label Sep 1, 2026
@neisw

neisw commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

/test unit

@neisw

neisw commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2026
@neisw

neisw commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

/pipeline required

@petr-muller

Copy link
Copy Markdown
Member

/test images

@petr-muller

Copy link
Copy Markdown
Member

/retest-required

@petr-muller

Copy link
Copy Markdown
Member

/test ?

@petr-muller

Copy link
Copy Markdown
Member

f**k me

• hook-apps received and processed both events; it is healthy. The failure is GitHub’s PR-files API, not webhook delivery.

  - /retest-required was received at 09:26:06Z, then Prow applied the retest-required filter.
  - /test ? was received at 09:26:45Z; it matched no jobs (to-trigger-count: 0).

  Both processing paths then failed on the same configured presubmit, pull-ci-openshift-origin-main-lint, while fetching PR changes:

  422 Unprocessable Entity:
  Server Error: Sorry, this diff is taking too long to generate.

  The PR is exceptionally large: 2 changed files, 529,312 additions, and 534,905 deletions. GitHub cannot generate the diff for GET /repos/openshift/origin/pulls/31581/files, and Prow aborts the whole comment event before creating a ProwJob or **replying.**

@petr-muller

Copy link
Copy Markdown
Member

/test agentic-images go-verify-deps images okd-scos-images

@petr-muller

Copy link
Copy Markdown
Member

kubernetes-sigs/prow#914

@petr-muller

Copy link
Copy Markdown
Member

/approved
/verified later @petr-muller

I want to see how Tide sees this one

@openshift-ci-robot openshift-ci-robot added verified-later verified Signifies that the PR passed pre-merge verification criteria labels Sep 1, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@petr-muller: This PR has been marked to be verified later by @petr-muller.

Details

In response to this:

/approved
/verified later @petr-muller

I want to see how Tide sees this one

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@petr-muller

Copy link
Copy Markdown
Member

/approve

@petr-muller

Copy link
Copy Markdown
Member

LOL I think approve is also path based and will run into a similar issue

@petr-muller

Copy link
Copy Markdown
Member

/label approved

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 1, 2026
@petr-muller

Copy link
Copy Markdown
Member

/hold

Seems like a PR like this becoming eligible to enter a merge pool will poison entire pool.

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 1, 2026
@petr-muller

Copy link
Copy Markdown
Member

/test lint unit verify verify-deps

@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

@openshift-ci[bot]: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@dgoodwin
dgoodwin merged commit 589a3d5 into main Sep 1, 2026
8 of 9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. ready-for-human-review Indicates a PR has been reviewed by automated tools and is ready for human review verified Signifies that the PR passed pre-merge verification criteria verified-later

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants