NO-JIRA: prove json patch

[openshift-trt-bot]

Job Failure Risk Analysis for sha: d5bcfa27922a50761afc339a65dbc568a819707e

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-ipsec-serial	High [sig-architecture] platform pods in ns/openshift-cluster-node-tuning-operator should not exit an excessive amount of times This test has passed 100.00% of 46 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days. --- [sig-architecture] platform pods in ns/openshift-ingress-canary should not exit an excessive amount of times This test has passed 100.00% of 46 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days. --- [sig-architecture] platform pods in ns/openshift-cluster-csi-drivers should not exit an excessive amount of times This test has passed 100.00% of 46 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days. --- [sig-architecture] platform pods in ns/openshift-network-diagnostics should not exit an excessive amount of times This test has passed 100.00% of 46 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days. --- Showing 4 of 12 test results
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade	Medium [bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above info This test has passed 93.53% of 232 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week. Open Bugs alert/KubeAPIErrorBudgetBurn should not be at or above info alert/KubeAPIErrorBudgetBurn should not be at or above info
pull-ci-openshift-origin-master-e2e-aws-ovn-kube-apiserver-rollout	Low [Conformance][Suite:openshift/kube-apiserver/rollout][Jira:"kube-apiserver"][sig-kube-apiserver] kube-apiserver should roll out new revisions without disruption [apigroup:config.openshift.io][apigroup:operator.openshift.io] This test has passed 61.54% of 13 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-kube-apiserver-rollout'] in the last 14 days.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 20c8f648eee9a8b6e7fe638d4127408ea68beed9

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-ipsec-serial	High [sig-architecture] platform pods in ns/openshift-kube-apiserver should not exit an excessive amount of times This test has passed 100.00% of 51 runs on jobs ['periodic-ci-openshift-release-master-ci-4.18-e2e-aws-ovn-serial' 'periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-serial'] in the last 14 days.
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade	Medium [bz-kube-apiserver][invariant] alert/KubeAPIErrorBudgetBurn should not be at or above info This test has passed 93.06% of 216 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week. Open Bugs alert/KubeAPIErrorBudgetBurn should not be at or above info alert/KubeAPIErrorBudgetBurn should not be at or above info

[openshift-ci-robot]

@p0lyn0mial: This pull request explicitly references no jira issue.

In response to [this](https://github.com/openshift/origin/pull/29163): > Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 41545785df6c6cbf3133d10ef1af4f4f2f95c290

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node	Medium [sig-node] static pods should start after being created This test has passed 85.19% of 54 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node'] in the last 14 days. Open Bugs Static pod controller pods sometimes fail to start

[deads2k]

/lgtm /approve

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, p0lyn0mial

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files: - ~~[OWNERS](https://github.com/openshift/origin/blob/master/OWNERS)~~ [deads2k] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 935bfac897732cf845b62413b236ecf86209e03d and 2 for PR HEAD 605eb0a38bda682c5328e7e003a060b47c6c9703 in total

[openshift-ci[bot]]

@p0lyn0mial: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	605eb0a38bda682c5328e7e003a060b47c6c9703	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-aws-ovn-single-node-serial	605eb0a38bda682c5328e7e003a060b47c6c9703	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn	605eb0a38bda682c5328e7e003a060b47c6c9703	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn-ipsec-serial	605eb0a38bda682c5328e7e003a060b47c6c9703	link	false	/test e2e-aws-ovn-ipsec-serial
ci/prow/e2e-aws-ovn-single-node	605eb0a38bda682c5328e7e003a060b47c6c9703	link	false	/test e2e-aws-ovn-single-node

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 605eb0a38bda682c5328e7e003a060b47c6c9703

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node	Medium [sig-node] static pods should start after being created This test has passed 93.88% of 49 runs on jobs ['periodic-ci-openshift-release-master-nightly-4.18-e2e-aws-ovn-single-node'] in the last 14 days. Open Bugs Static pod controller pods sometimes fail to start

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 935bfac897732cf845b62413b236ecf86209e03d and 2 for PR HEAD 605eb0a38bda682c5328e7e003a060b47c6c9703 in total

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.18.0-202410151043.p0.g65c5d9d.assembly.stream.el9. All builds following this will include this PR.