[release-4.13] OCPBUGS-77468: go mod vendor for 4.13 by fgallott · Pull Request #2618 · openshift/kubernetes

fgallott · 2026-03-09T14:04:16Z

same as #2615

openshift-ci-robot · 2026-03-09T14:04:25Z

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

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

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 · 2026-03-09T14:04:28Z

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

f7090db|hermetic 4.13: 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 · 2026-03-09T14:05:54Z

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: dae31d3a-6c4b-4a19-968a-ba0891e61e8a

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

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

openshift-ci · 2026-03-09T14:15:13Z

[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 tkashem 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 · 2026-03-10T08:26:00Z

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

0b04bf8|UPSTREAM: : hermetic 4.13: 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 · 2026-03-30T07:41:34Z

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

8ab3c93|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
9b84c64|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
bf94297|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
ca31232|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
d6e752f|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.

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

openshift-ci-robot · 2026-03-30T07:43:52Z

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

203ee65|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
2e279d8|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
ab76e6d|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 · 2026-03-30T08:58:03Z

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

2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
49482ba|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
ab76e6d|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
e34c478|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 · 2026-03-30T09:22:34Z

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

123763a|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
ab76e6d|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
be209cc|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 · 2026-03-30T09:34:57Z

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

123763a|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
3f12a05|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
ab76e6d|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 · 2026-03-30T10:57:08Z

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

2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
acd199f|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
d8c6314|UPSTREAM: : run hack/update-vendor.sh: does not specify an upstream backport in the commit message
fb5aec3|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 · 2026-03-30T11:15:11Z

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

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

Details

In response to this:

same as #2615

successful build with these changes

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 · 2026-03-30T12:31:35Z

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

2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
2820338|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
7826280|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
cf61f44|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.

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

openshift-ci-robot · 2026-03-30T13:21:55Z

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

2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
517af58|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
cd5f9b1|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
fb44244|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.

fgallott · 2026-03-30T17:59:03Z

/test e2e-aws-ovn-serial

fgallott · 2026-04-03T06:50:44Z

/test e2e-aws-ovn-serial

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

openshift-ci-robot · 2026-04-13T08:31:26Z

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

2459d39|UPSTREAM: : fix staging test discovery after hermetic vendor: does not specify an upstream backport in the commit message
360a699|UPSTREAM: : update hack/update-vendor.sh: does not specify an upstream backport in the commit message
517af58|UPSTREAM: : fix unit tests: does not specify an upstream backport in the commit message
64a9649|UPSTREAM: : switch to -mod=readonly: does not specify an upstream backport in the commit message
cd5f9b1|UPSTREAM: : fix verify after hermetic vendor: does not specify an upstream backport in the commit message
fb44244|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.

fgallott · 2026-04-13T11:53:03Z

/test e2e-aws-ovn-cgroupsv2

openshift-ci · 2026-04-13T14:50:11Z

@fgallott: 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/e2e-aws-ovn-serial	`64a9649`	link	true	`/test e2e-aws-ovn-serial`

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.

fgallott · 2026-04-22T15:28:11Z

/hold

fgallott · 2026-04-22T18:41:30Z

/close

openshift-ci-robot · 2026-04-22T18:41:44Z

@fgallott: This pull request references Jira Issue OCPBUGS-77468. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

Details

In response to this:

same as #2615

successful build with these changes

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 · 2026-04-22T18:41:45Z

@fgallott: Closed this PR.

Details

In response to this:

/close

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 Bot requested review from deads2k and tkashem March 9, 2026 14:14

openshift-ci Bot added the vendor-update Touching vendor dir or related files label Mar 9, 2026

fgallott force-pushed the hermetic-4.13 branch from f7090db to 0b04bf8 Compare March 10, 2026 08:25

fgallott force-pushed the hermetic-4.13 branch from 0b04bf8 to bf94297 Compare March 30, 2026 07:41

openshift-ci Bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 30, 2026

fgallott added 2 commits March 30, 2026 09:42

UPSTREAM: <carry>: update hack/update-vendor.sh

360a699

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

UPSTREAM: <carry>: fix staging test discovery after hermetic vendor

2459d39

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

fgallott force-pushed the hermetic-4.13 branch from bf94297 to 2e279d8 Compare March 30, 2026 07:43

openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 30, 2026

fgallott force-pushed the hermetic-4.13 branch from 2e279d8 to e34c478 Compare March 30, 2026 08:57

fgallott force-pushed the hermetic-4.13 branch from e34c478 to be209cc Compare March 30, 2026 09:22

fgallott force-pushed the hermetic-4.13 branch from be209cc to 3f12a05 Compare March 30, 2026 09:34

fgallott force-pushed the hermetic-4.13 branch from 3f12a05 to d8c6314 Compare March 30, 2026 10:56

fgallott force-pushed the hermetic-4.13 branch from d8c6314 to cf61f44 Compare March 30, 2026 12:31

fgallott added 3 commits March 30, 2026 15:21

UPSTREAM: <carry>: fix unit tests

517af58

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

UPSTREAM: <carry>: fix verify after hermetic vendor

cd5f9b1

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

UPSTREAM: <drop>: run hack/update-vendor.sh

fb44244

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

fgallott force-pushed the hermetic-4.13 branch from cf61f44 to fb44244 Compare March 30, 2026 13:21

UPSTREAM: <carry>: switch to -mod=readonly

64a9649

rh-pre-commit.version: 2.3.2 rh-pre-commit.check-secrets: ENABLED

dfajmon mentioned this pull request Apr 21, 2026

[release-4.13] OCPBUGS-77660: Skip E2e: attach on previously attached volumes should work #2606

Open

openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Apr 22, 2026

openshift-ci Bot closed this Apr 22, 2026

fgallott deleted the hermetic-4.13 branch April 23, 2026 09:48

Conversation

fgallott commented Mar 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

openshift-ci-robot commented Mar 9, 2026

Uh oh!

openshift-ci-robot commented Mar 9, 2026

Uh oh!

coderabbitai Bot commented Mar 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Uh oh!

openshift-ci Bot commented Mar 9, 2026

Uh oh!

openshift-ci-robot commented Mar 10, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

openshift-ci-robot commented Mar 30, 2026

Uh oh!

fgallott commented Mar 30, 2026

Uh oh!

fgallott commented Apr 3, 2026

Uh oh!

openshift-ci-robot commented Apr 13, 2026

Uh oh!

fgallott commented Apr 13, 2026

Uh oh!

openshift-ci Bot commented Apr 13, 2026

Uh oh!

fgallott commented Apr 22, 2026

Uh oh!

fgallott commented Apr 22, 2026

Uh oh!

openshift-ci-robot commented Apr 22, 2026

Uh oh!

openshift-ci Bot commented Apr 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

fgallott commented Mar 9, 2026 •

edited

Loading

coderabbitai Bot commented Mar 9, 2026 •

edited

Loading