OCPBUGS-69688: Synchronize From Upstream Repositories

[openshift-bot]

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date	Commit	Author	Message
2026-01-20 15:06:35	operator-framework/operator-lifecycle-manager@74911fc	dependabot[bot]	🌱 Bump github.com/sirupsen/logrus from 1.9.3 to 1.9.4 (#3740)
2026-01-20 16:08:14	operator-framework/operator-lifecycle-manager@34ea6ce	Jian Zhang	Fix nil pointer dereference panic in event recorder (#3727)
2026-01-20 20:00:49	operator-framework/operator-lifecycle-manager@afb9e80	Camila Macedo	Add e2e test for operator workload persistence after catalog deletion (#3737)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

[openshift-ci-robot]

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

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date	Commit	Author	Message
2026-01-20 15:06:35	operator-framework/operator-lifecycle-manager@74911fc	dependabot[bot]	🌱 Bump github.com/sirupsen/logrus from 1.9.3 to 1.9.4 (#3740)
2026-01-20 16:08:14	operator-framework/operator-lifecycle-manager@34ea6ce	Jian Zhang	Fix nil pointer dereference panic in event recorder (#3727)
2026-01-20 20:00:49	operator-framework/operator-lifecycle-manager@afb9e80	Camila Macedo	Add e2e test for operator workload persistence after catalog deletion (#3737)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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-bot: GitHub didn't allow me to request PR reviews from the following users: openshift/openshift-team-operator-framework.

Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs.

Details

In response to this:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date	Commit	Author	Message
2026-01-20 15:06:35	operator-framework/operator-lifecycle-manager@74911fc	dependabot[bot]	🌱 Bump github.com/sirupsen/logrus from 1.9.3 to 1.9.4 (#3740)
2026-01-20 16:08:14	operator-framework/operator-lifecycle-manager@34ea6ce	Jian Zhang	Fix nil pointer dereference panic in event recorder (#3727)
2026-01-20 20:00:49	operator-framework/operator-lifecycle-manager@afb9e80	Camila Macedo	Add e2e test for operator workload persistence after catalog deletion (#3737)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-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:

• DOWNSTREAM_OWNERS

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: openshift-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:

• DOWNSTREAM_OWNERS

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

[jianzhangbjz]

/retitle OCPBUGS-69688: Synchronize From Upstream Repositories

[openshift-ci-robot]

@openshift-bot: This pull request references Jira Issue OCPBUGS-69688, which is invalid:

• expected the bug to target the "4.22.0" version, but no target version was set

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:

The staging/ and vendor/ directories have been synchronized from the upstream repositories, pulling in the following commits:

Date	Commit	Author	Message
2026-01-20 15:06:35	operator-framework/operator-lifecycle-manager@74911fc	dependabot[bot]	🌱 Bump github.com/sirupsen/logrus from 1.9.3 to 1.9.4 (#3740)
2026-01-20 16:08:14	operator-framework/operator-lifecycle-manager@34ea6ce	Jian Zhang	Fix nil pointer dereference panic in event recorder (#3727)
2026-01-20 20:00:49	operator-framework/operator-lifecycle-manager@afb9e80	Camila Macedo	Add e2e test for operator workload persistence after catalog deletion (#3737)

This pull request is expected to merge without any human intervention. If tests are failing here, changes must land upstream to fix any issues so that future downstreaming efforts succeed.

/cc @openshift/openshift-team-operator-framework

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.

[jianzhangbjz]

/payload-job periodic-ci-openshift-release-master-ci-4.22-e2e-azure-ovn-upgrade

[openshift-ci]

@jianzhangbjz: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.22-e2e-azure-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d897af20-f663-11f0-93b9-7e6a1414279a-0

[jianzhangbjz]

/jira refresh

[openshift-ci-robot]

@jianzhangbjz: This pull request references Jira Issue OCPBUGS-69688, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

No GitHub users were found matching the public email listed for the QA contact in Jira (jiazha@redhat.com), skipping review request.

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.

[jianzhangbjz]

/test e2e-gcp-olm

[jianzhangbjz]

Test passed. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-operator-framework-olm-1201-ci-4.22-e2e-azure-ovn-upgrade/2013777387895918592
/verified by @jianzhangbjz

[openshift-ci-robot]

@jianzhangbjz: This PR has been marked as verified by @jianzhangbjz.

Details

In response to this:

Test passed. https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-operator-framework-olm-1201-ci-4.22-e2e-azure-ovn-upgrade/2013777387895918592
/verified by @jianzhangbjz

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

/retest-required

Remaining retests: 0 against base HEAD 8cfcfeb and 2 for PR HEAD fa8fb0a in total

[openshift-ci]

@openshift-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-gcp-olm	fa8fb0a	link	true	/test e2e-gcp-olm

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.

[tmshort]

/retest