OCPBUGS-67286: [release-4.18] Fix incomplete vendor/

[adobes1]

Hermetic builds require that running go mod vendor produces no diff. Without this PR, ART can't build ose-ibmcloud-cluster-api-controllers hermetically.

The changes in this PR are the result of running go mod vendor and ensuring that the vendored file is commited and not ignored by .gitignore

[openshift-ci]

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

[prb112]

Hey @adobes1 when ready please assign @Karthik-K-N for review.

[openshift-ci-robot]

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

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-67285 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 require that running go mod vendor produces no diff. Without this PR, ART can't build ose-ibmcloud-cluster-api-controllers hermetically.

The changes in this PR are the result of running go mod vendor and ensuring that the vendored file is commited and not ignored by .gitignore

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.

[adobes1]

/jira refresh

[openshift-ci-robot]

@adobes1: This pull request references Jira Issue OCPBUGS-67286, 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.18.z) matches configured target version for branch (4.18.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-67285 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-67285 targets the "4.19.z" version, which is one of the valid target versions: 4.19.0, 4.19.z
• bug has dependents

Requesting review from QA contact:
/cc @sunzhaohua2

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.

[adobes1]

/assign Karthik-K-N

[Karthik-K-N]

@adobes1 Thanks for the PR, I know its already been fixed in the main/recent branches via PR #112

Does it need to be added for all the other branches, because I dont this we support till 4.12.
/cc @RadekManak

[adobes1]

Hi @Karthik-K-N! OCP has an exception for being non-hermetic which expires on January 30th, 2026. Since 4.12 goes EOL on January 17, 2026, we should be able to skip that. I'm not too sure about 4.13 since that is a bit of a special case but I will ask around for clarification.

We need to get this fix in for all the other versions (4.14 to 4.18) since ose-ibmcloud-cluster-api-controllers will continue to be shipped in those versions

[Karthik-K-N]

/lgtm
/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Karthik-K-N
Once this PR has been reviewed and has the lgtm label, please assign radekmanak 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:

• OWNERS

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

[sunzhaohua2]

/verified by @sunzhaohua2

[openshift-ci-robot]

@sunzhaohua2: This PR has been marked as verified by @sunzhaohua2.

Details

In response to this:

/verified by @sunzhaohua2

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.