[release-5.0] OCPBUGS-122387: Bump google.golang.org/protobuf to v1.36.12

[redhat-chai-bot]

This is an automated cherry-pick of #1264

/assign Prashanth684

Backport summary

• OCPBUGS-122387 backports OCPBUGS-114428 to release-5.0

Cherry-picked commits (merge): c533c03

---

AI-generated. Review for accuracy.

@Prashanth684 requested in Slack thread

[openshift-merge-bot]

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: LGTM mode

[openshift-ci-robot]

@redhat-chai-bot: Detected clone of Jira Issue OCPBUGS-114428 with correct target version. Will retitle the PR to link to the clone.
/retitle [release-5.0] OCPBUGS-122387: Bump google.golang.org/protobuf to v1.36.12

Details

In response to this:

This is an automated cherry-pick of #1264

/assign Prashanth684

Backport summary

• OCPBUGS-122387 backports OCPBUGS-114428 to release-5.0

Cherry-picked commits (merge): c533c03

---

AI-generated. Review for accuracy.

@Prashanth684 requested in Slack thread

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.

[redhat-chai-bot]

/jira refresh

[openshift-ci-robot]

@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-122387, which is invalid:

• expected dependent Jira Issue OCPBUGS-114428 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

/jira refresh

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.

[jgbernalp]

/jira refresh

[openshift-ci-robot]

@jgbernalp: This pull request references Jira Issue OCPBUGS-122387, which is valid.

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (5.0.0) matches configured target version for branch (5.0.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-114428 is in the state ON_QA, which is one of the valid states (MODIFIED, ON_QA, VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-114428 targets the "5.1.0" version, which is one of the valid target versions: 5.1.0
• bug has dependents

Details

In response to this:

/jira refresh

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.

[jgbernalp]

/lgtm
/labell qe-approved

[openshift-merge-bot]

Scheduling required tests:
/test e2e-agnostic-cmo
/test e2e-monitoring

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, redhat-chai-bot

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [jgbernalp]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[redhat-chai-bot]

/test e2e-monitoring

---

AI-generated. Review for accuracy.

[redhat-chai-bot]

/test e2e-monitoring

---

AI-generated. Review for accuracy.

[openshift-ci]

@redhat-chai-bot: The following test 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-monitoring	b6db30d	link	true	/test e2e-monitoring

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.

[etmurasaki]

if you look at https://amd64.ocp.releases.ci.openshift.org/releasestream/5.0.0-0.nightly/release/5.0.0-0.nightly-2026-09-28-094035 then aws-console test failed: https://prow.ci.openshift.org/view/gs/test-platform-results-public/logs/periodic-ci-openshift-release-main-nightly-5.0-console-aws/2104508797316763648 for weeks and in testing clusters it is only possible to perform UI testing reliably with registry.ci.openshift.org/ocp/release-5:5.0.0-0.nightly-2026-09-23-031212. Other newer builds shows the same blocker presented in our tests.

[redhat-chai-bot]

Thanks for the nightly comparison. I checked the linked console-aws run and the three e2e-monitoring runs on this PR. All three PR runs fail in the Cypress session setup while waiting for [data-test="Operators"], before the plugin-specific tests execute. The linked console-aws job also fails, but its Playwright errors involve other page elements; it does not establish that the two jobs have the same root cause. The Sept 23 nightly likewise had some console-aws failures, although later nightlies have substantially more failures, so the console-side degradation is useful context.

I won't run another blind retry. If there is a comparison showing that this exact selector succeeds on the older payload and fails on a newer one with the same test setup, that would help isolate a console/payload change from a test-harness mismatch.

---

AI-generated. Review for accuracy.

---

AI-generated. Review for accuracy.

[openshift-ci-robot]

@redhat-chai-bot: Jira Issue OCPBUGS-122387: Some pull requests linked via external trackers have merged:

• openshift/oauth-server#261
• openshift/oauth-apiserver#229
• openshift/cluster-kube-apiserver-operator#2311
• openshift/cluster-authentication-operator#998
• openshift/cluster-bootstrap#147
• openshift/cluster-openshift-apiserver-operator#771
• openshift/cluster-kube-controller-manager-operator#968
• openshift/must-gather#564
• openshift/cluster-config-operator#502
• openshift/cluster-kube-scheduler-operator#677
• openshift/kubernetes-kube-storage-version-migrator#260
• openshift/azure-kubernetes-kms#66

The following pull request, linked via external tracker, has not merged:

• openshift/cloud-provider-kubevirt#99 is open

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-122387 has not been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #1264

/assign Prashanth684

Backport summary

• OCPBUGS-122387 backports OCPBUGS-114428 to release-5.0

Cherry-picked commits (merge): c533c03

---

AI-generated. Review for accuracy.

@Prashanth684 requested in Slack thread

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-merge-robot]

Fix included in release 5.0.0-0.nightly-2026-10-01-030312