Skip to content

[release-4.17] OCPBUGS-77266: Fix incomplete vendor/#634

Open
adobes1 wants to merge 1 commit intoopenshift:release-4.17from
adobes1:4.17-fix-vendor
Open

[release-4.17] OCPBUGS-77266: Fix incomplete vendor/#634
adobes1 wants to merge 1 commit intoopenshift:release-4.17from
adobes1:4.17-fix-vendor

Conversation

@adobes1
Copy link
Contributor

@adobes1 adobes1 commented Feb 25, 2026

Hermetic builds in Konflux require that running go mod vendor produces no diff. Without this PR, ART can't build dpu-operator, dpu-cni and dpu-daemon hermetically.

The changes in this PR are the result of running go mod tidy and go mod vendor

@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 Feb 25, 2026
@openshift-ci-robot
Copy link

@adobes1: This pull request references Jira Issue OCPBUGS-77266, which is invalid:

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

Hermetic builds in Konflux require that running go mod vendor produces no diff. Without this PR, ART can't build dpu-operator, dpu-cni and dpu-daemon hermetically.

The changes in this PR are the result of running go mod tidy and 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 bn222 and wizhaoredhat February 25, 2026 10:09
@adobes1
Copy link
Contributor Author

adobes1 commented Feb 25, 2026

/retest

@adobes1
Copy link
Contributor Author

adobes1 commented Feb 25, 2026

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Feb 25, 2026
@openshift-ci-robot
Copy link

@adobes1: This pull request references Jira Issue OCPBUGS-77266, 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.17.z) matches configured target version for branch (4.17.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-77265 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-77265 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
  • bug has dependents

Requesting review from QA contact:
/cc @zhiqiangf

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.

@openshift-ci-robot openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Feb 25, 2026
@openshift-ci openshift-ci bot requested a review from zhiqiangf February 25, 2026 11:41
@fgallott
Copy link

@wizhaoredhat may you have a look at this one as well? thank you!

@wizhaoredhat
Copy link
Contributor

/lgtm

@wizhaoredhat
Copy link
Contributor

/approve

@wizhaoredhat
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Mar 10, 2026
@wizhaoredhat
Copy link
Contributor

/bypass verified

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2026
@openshift-ci
Copy link

openshift-ci bot commented Mar 10, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adobes1, wizhaoredhat

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:

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 added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 10, 2026
@fgallott
Copy link

/retest

@openshift-ci
Copy link

openshift-ci bot commented Mar 12, 2026

@adobes1: 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/images 7d90fa8 link true /test images
ci/prow/make-e2e-test-marvell 7d90fa8 link true /test make-e2e-test-marvell
ci/prow/make-e2e-test 7d90fa8 link true /test make-e2e-test
ci/prow/make-test 7d90fa8 link true /test make-test

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

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants