Skip to content

[release-4.19] OCPBUGS-89927: patching golang.org/x/crypto with sustaining/crypto@v0.41.0-sec.3 - #10762

Open
moebasim wants to merge 1 commit into
openshift:release-4.19from
moebasim:release-4.19
Open

[release-4.19] OCPBUGS-89927: patching golang.org/x/crypto with sustaining/crypto@v0.41.0-sec.3#10762
moebasim wants to merge 1 commit into
openshift:release-4.19from
moebasim:release-4.19

Conversation

@moebasim

@moebasim moebasim commented Aug 12, 2026

Copy link
Copy Markdown

Go version for ocp-4.19 is v1.23.2
applying replace golang.org/x/crypto with sustaining/crypto@v0.33.0-sec.2 patch

Commands used :

go mod edit -replace golang.org/x/crypto=github.com/openshift-sustaining/crypto@v0.41.0-sec.3
go mod tidy
go mod vendor

@openshift-merge-bot

openshift-merge-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

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 openshift-ci-robot added 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 Aug 12, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

@moebasim: This pull request references Jira Issue OCPBUGS-39829, which is invalid:

  • expected the bug to be open, but it isn't
  • expected the vulnerability to target either version "4.19.z." or "openshift-4.19.z.", but it targets "4.14.z" instead
  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is Closed (Not a Bug) instead
  • 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-39829 to depend on a bug targeting a version in 4.20.0, 4.20.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:

Go version for ocp-4.19 is v1.23.2
applying replace golang.org/x/crypto with sustaining/crypto@v0.33.0-sec.2 patch

Commands used :

go mod edit -replace golang.org/x/crypto=github.com/openshift-sustaining/crypto@v0.41.0-sec.3
go mod tidy
go mod vendor

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.

@coderabbitai

coderabbitai Bot commented Aug 12, 2026

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 2cb9e3ed-d3c0-4426-a0f0-8c050b6ab2c3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@moebasim moebasim changed the title [release-4.19] OCPBUGS-39829: patching golang.org/x/crypto with sustaining/crypto@v0.41.0-sec.3 [release-4.19] OCPBUGS-89927: patching golang.org/x/crypto with sustaining/crypto@v0.41.0-sec.3 Aug 12, 2026
@openshift-ci-robot openshift-ci-robot added the jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. label Aug 12, 2026
@openshift-ci-robot

openshift-ci-robot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

@moebasim: This pull request references Jira Issue OCPBUGS-89927, which is invalid:

  • expected dependent Jira Issue OCPBUGS-90004 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.

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

Details

In response to this:

Go version for ocp-4.19 is v1.23.2
applying replace golang.org/x/crypto with sustaining/crypto@v0.33.0-sec.2 patch

Commands used :

go mod edit -replace golang.org/x/crypto=github.com/openshift-sustaining/crypto@v0.41.0-sec.3
go mod tidy
go mod vendor

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 barbacbd and sadasu August 12, 2026 13:47
@openshift-ci

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign sadasu 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

@openshift-ci

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown
Contributor

@moebasim: 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/images bd86cf4 link true /test images

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.

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

Reviewers

@barbacbd barbacbd Awaiting requested review from barbacbd
@sadasu sadasu Awaiting requested review from sadasu

Assignees

No one assigned

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-important Referenced Jira bug's severity is important 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

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@moebasim @openshift-ci-robot