[release-4.15] OCPBUGS-77466: go mod vendor for 4.15

[fgallott]

same as #2615

[openshift-ci-robot]

@fgallott: This pull request references Jira Issue OCPBUGS-77466, which is invalid:

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

same as #2615

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]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• d30a128|hermetic 4.15: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[coderabbitai]

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: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 22827b6c-79dc-46ed-a056-1ca1428ae602

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fgallott
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:

• DOWNSTREAM_OWNERS

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

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 68fc11e|UPSTREAM: : hermetic 4.15: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 276af6f|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 56da54d|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 618f37c|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
• 73a03c6|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
• 7a3e27a|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 276af6f|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 618f37c|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
• 73a03c6|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
• 7a3e27a|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
• ff3ea43|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 276af6f|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 2e0f3be|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 618f37c|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
• 73a03c6|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
• 7a3e27a|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 276af6f|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 44ebadf|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
• 58cae9f|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
• 73a03c6|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
• e4afa67|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 276af6f|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 58cae9f|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
• 73a03c6|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
• 78c6341|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
• d138ccf|wip: does not specify an upstream backport in the commit message
• f18508f|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 1dd6570|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
• 276af6f|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 6fed16d|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 73a03c6|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
• 73ffdf8|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@fgallott: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• 1dd6570|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
• 276af6f|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 6fed16d|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
• 73a03c6|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
• 73ffdf8|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
• db92e69|UPSTREAM: : switch to -mod=readonly: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci]

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