[release-4.13] OCPBUGS-67695: chore: CVE-2025-65637: bump sirupsen/logrus to 1.9.3

[rhdmalone]

1. go lang changes only so there was no need to run ./scripts/rh-manifest.sh for node
2. Fixes #OCPBUGS-67695
3. Jira OCPBUGS-67695 https://issues.redhat.com/browse/OCPBUGS-67695
4. GHSA-4f99-4q7p-p3gh: bump sirupsen/logrus to 1.9.3
5. scrape/testdata/gencert/*
   This directory contains tools to regenerate TLS certificates used by scrape and tracing tests only. It is not built or tested by the Go toolchain (Go ignores testdata). See scrape/testdata/gencert/README.md for more details

[openshift-ci-robot]

@rhdmalone: This pull request references Jira Issue OCPBUGS-67695, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected Jira Issue OCPBUGS-67695 to depend on a bug targeting a version in 4.14.0, 4.14.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

1. go lang changes only so there was no need to run ./scripts/rh-manifest.sh for node
2. Fixes #OCPBUGS-67695
3. Jira OCPBUGS-67695 https://issues.redhat.com/browse/OCPBUGS-67695
4. GHSA-4f99-4q7p-p3gh: bump sirupsen/logrus to 1.9.3
5. includes git cherry-pick 1435c8a to get updated test certificates

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.

[rhdmalone]

/jira refresh

[openshift-ci-robot]

@rhdmalone: This pull request references Jira Issue OCPBUGS-67695, which is invalid:

• expected Jira Issue OCPBUGS-67695 to depend on a bug targeting a version in 4.14.0, 4.14.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

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.

[rhdmalone]

/jira refresh

[openshift-ci-robot]

@rhdmalone: This pull request references Jira Issue OCPBUGS-67695, which is invalid:

• expected dependent Jira Issue OCPBUGS-76414 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is Closed (Not a Bug) 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.

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.

[rhdmalone]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

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

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@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.

[juzhao]

/verified by @juzhao

[openshift-ci-robot]

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

Details

In response to this:

/verified by @juzhao

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.

[juzhao]

needs openshift/cluster-monitoring-operator#2813 to be merged

[rhdmalone]

/test e2e-agnostic-cmo

[rhdmalone]

/test e2e-agnostic-cmo

[rhdmalone]

/test e2e-agnostic-cmo

[rhdmalone]

/test e2e-agnostic-cmo

[rhdmalone]

/test e2e-agnostic-cmo

[simonpasquier]

/test e2e-agnostic-cmo

[simonpasquier]

/approve
/lgtm
/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rhdmalone, simonpasquier

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 [simonpasquier]

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

[simonpasquier]

/label backport-risk-assessed

[openshift-ci-robot]

@rhdmalone: An error was encountered invalid pull identifier with 2 parts: "mjuanxd/logrus-dos-poc" for bug OCPBUGS-67695 on the Jira server at https://issues.redhat.com/. No known errors were detected, please see the full error message for details.

Full error message.

Please contact an administrator to resolve this issue, then request a bug refresh with /jira refresh.Jira Issue Verification Checks: Jira Issue OCPBUGS-67695
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-67695 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

1. go lang changes only so there was no need to run ./scripts/rh-manifest.sh for node
2. Fixes #OCPBUGS-67695
3. Jira OCPBUGS-67695 https://issues.redhat.com/browse/OCPBUGS-67695
4. GHSA-4f99-4q7p-p3gh: bump sirupsen/logrus to 1.9.3
5. scrape/testdata/gencert/*
   This directory contains tools to regenerate TLS certificates used by scrape and tracing tests only. It is not built or tested by the Go toolchain (Go ignores testdata). See scrape/testdata/gencert/README.md for more 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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

@rhdmalone: 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-aws-ovn	0cc5182	link	unknown	/test e2e-aws-ovn
ci/prow/e2e-aws-ovn-upgrade	0cc5182	link	unknown	/test e2e-aws-ovn-upgrade

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.

[openshift-merge-robot]

Fix included in accepted release 4.13.0-0.nightly-2026-02-19-033642