Skip to content

OCPBUGS-78009: fix vendor for hermetic 4.13#1175

Merged
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.13from
fgallott:hermetic-4.13
Mar 16, 2026
Merged

OCPBUGS-78009: fix vendor for hermetic 4.13#1175
openshift-merge-bot[bot] merged 2 commits intoopenshift:release-4.13from
fgallott:hermetic-4.13

Conversation

@fgallott
Copy link
Copy Markdown

ART can't build sriov-network-operator hermetically, versions openshift-4.13 backwards

The following is the error:

Error: PackageRejected: The content of the vendor directory is not consistent with go.mod. Please check the logs for more details.
  Please try running `go mod vendor` and committing the changes.
  Note that you may need to `git add --force` ignored files in the vendor/ dir.

@fgallott
Copy link
Copy Markdown
Author

fgallott commented Mar 2, 2026

/retest

@fgallott
Copy link
Copy Markdown
Author

fgallott commented Mar 9, 2026

/jira cherrypick OCPBUGS-78007

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: Jira Issue OCPBUGS-78007 has been cloned as Jira Issue OCPBUGS-78009. Will retitle bug to link to clone.
/retitle OCPBUGS-78009: fix vendor for hermetic 4.13

Details

In response to this:

/jira cherrypick OCPBUGS-78007

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 changed the title fix vendor for hermetic 4.13 OCPBUGS-78009: fix vendor for hermetic 4.13 Mar 9, 2026
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Mar 9, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: This pull request references Jira Issue OCPBUGS-78009, 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 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-78007 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-78007 targets the "4.14.z" version, which is one of the valid target versions: 4.14.0, 4.14.z
  • bug has dependents

Requesting review from QA contact:
/cc @zhiqiangf

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

Details

In response to this:

ART can't build sriov-network-operator hermetically, versions openshift-4.13 backwards

The following is the error:

Error: PackageRejected: The content of the vendor directory is not consistent with go.mod. Please check the logs for more details.
 Please try running `go mod vendor` and committing the changes.
 Note that you may need to `git add --force` ignored files in the vendor/ dir.

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 added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Mar 9, 2026
@openshift-ci openshift-ci Bot requested a review from zhiqiangf March 9, 2026 14:20
@fgallott
Copy link
Copy Markdown
Author

/retest-required

rh-pre-commit.version: 2.3.2
rh-pre-commit.check-secrets: ENABLED
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 12, 2026

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

@zeeke
Copy link
Copy Markdown
Contributor

zeeke commented Mar 16, 2026

/lgtm
/approve
/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 16, 2026
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Mar 16, 2026
@fgallott
Copy link
Copy Markdown
Author

/verified by CI

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Mar 16, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: This PR has been marked as verified by CI.

Details

In response to this:

/verified by CI

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.

@wizhaoredhat
Copy link
Copy Markdown
Contributor

/approve

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 16, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: fgallott, wizhaoredhat, zeeke

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 16, 2026
@openshift-merge-bot openshift-merge-bot Bot merged commit 16d7a2d into openshift:release-4.13 Mar 16, 2026
8 checks passed
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fgallott: Jira Issue OCPBUGS-78009: All pull requests linked via external trackers have merged:

All linked pull requests have the verified tag. Jira Issue OCPBUGS-78009 has been moved to the VERIFIED state.

Details

In response to this:

ART can't build sriov-network-operator hermetically, versions openshift-4.13 backwards

The following is the error:

Error: PackageRejected: The content of the vendor directory is not consistent with go.mod. Please check the logs for more details.
 Please try running `go mod vendor` and committing the changes.
 Note that you may need to `git add --force` ignored files in the vendor/ dir.

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.

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. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants