Skip to content

OCPBUGS-67465: bump github.com/sirupsen/logrus to v1.9.3#164

Open
jkaurredhat wants to merge 1 commit intoopenshift:release-4.12from
jkaurredhat:update-logrus-4.12
Open

OCPBUGS-67465: bump github.com/sirupsen/logrus to v1.9.3#164
jkaurredhat wants to merge 1 commit intoopenshift:release-4.12from
jkaurredhat:update-logrus-4.12

Conversation

@jkaurredhat
Copy link

@jkaurredhat jkaurredhat commented Jan 6, 2026

Backport #163

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Jan 6, 2026
@openshift-ci-robot
Copy link
Contributor

@jkaurredhat: This pull request references Jira Issue OCPBUGS-67465, 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 dependent Jira Issue OCPBUGS-67464 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 (Duplicate) instead
  • expected dependent Jira Issue OCPBUGS-67464 to target a version in 4.13.0, 4.13.z, but it targets "4.12.z" 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:

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 requested review from jsafrane and tsmetana January 6, 2026 16:04
@openshift-ci-robot
Copy link
Contributor

@jkaurredhat: This pull request references Jira Issue OCPBUGS-67465, which is invalid:

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

Backport #163

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.

@jkaurredhat
Copy link
Author

/retest-required

@jkaurredhat
Copy link
Author

/test e2e-gcp-csi

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 18, 2026

@jkaurredhat: 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.

@germanparente
Copy link

since this is related to CVE fix and eus I am approving it:

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 19, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: germanparente, jkaurredhat
Once this PR has been reviewed and has the lgtm label, please assign bertinatto for approval. For more information see the Code Review Process.

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

Details Needs approval from an approver in each of these files:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants