Skip to content

[release-4.18] OCPBUGS-103472: Replace golang.org/x/net with github.com/openshift-sustaining/net@v0.35.0-sec.3 - #153

Open
sunku5494 wants to merge 2 commits into
openshift:release-4.18from
sunku5494:net-4.18
Open

[release-4.18] OCPBUGS-103472: Replace golang.org/x/net with github.com/openshift-sustaining/net@v0.35.0-sec.3#153
sunku5494 wants to merge 2 commits into
openshift:release-4.18from
sunku5494:net-4.18

Conversation

@sunku5494

Copy link
Copy Markdown

address CVE-2026-33814

…staining/net@v0.35.0-sec.3 to address CVE-2026-33814

Signed-off-by: Venkata Charan Sunku <vsunku@redhat.com>
@openshift-merge-bot

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/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. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 31, 2026
@openshift-ci-robot

Copy link
Copy Markdown
Contributor

@sunku5494: This pull request references Jira Issue OCPBUGS-103472, which is invalid:

  • expected dependent Jira Issue OCPBUGS-103710 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:

address CVE-2026-33814

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 31, 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: 7014e48e-6733-4b55-873c-e11954becd03

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.

@openshift-ci
openshift-ci Bot requested review from bpickard22 and fedepaol August 31, 2026 15:17
@shannon

shannon commented Aug 31, 2026

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Aug 31, 2026
@openshift-merge-bot

Copy link
Copy Markdown
Contributor

Scheduling required tests:
/test e2e-gcp

@openshift-ci

openshift-ci Bot commented Aug 31, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The get_tools.sh installs golint into BIN_DIR via GOBIN, but
check_golint.sh invokes it as a bare command. On the Go 1.22
builder (release-4.18) BIN_DIR is not in PATH, causing
'golint: command not found'. Exporting PATH fixes this
consistently across all Go versions.
@sunku5494

Copy link
Copy Markdown
Author

/test pull-ci-openshift-network-metrics-daemon-release-4.18-unit

@openshift-ci openshift-ci Bot removed the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2026
@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown

New changes are detected. LGTM label has been removed.

@openshift-ci

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown

@sunku5494: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test e2e-gcp
/test images
/test unit

The following commands are available to trigger optional jobs:

/test security

Use /test all to run the following jobs that were automatically triggered:

pull-ci-openshift-network-metrics-daemon-release-4.18-images
pull-ci-openshift-network-metrics-daemon-release-4.18-security
pull-ci-openshift-network-metrics-daemon-release-4.18-unit
Details

In response to this:

/test pull-ci-openshift-network-metrics-daemon-release-4.18-unit

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

openshift-ci Bot commented Sep 1, 2026

Copy link
Copy Markdown

@sunku5494: 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/security b3c8c26 link false /test security
ci/prow/unit b3c8c26 link true /test unit

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

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

Development

Successfully merging this pull request may close these issues.

3 participants