Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cluster: Allow kubevirtci tag overriding #319

Merged
merged 2 commits into from
Jul 3, 2024

Conversation

oshoval
Copy link
Member

@oshoval oshoval commented Jul 3, 2024

What this PR does / why we need it:
It is helpful either manually or for example
when used from CNAO, to use same tag of the cluster that CNAO deployed.
Otherwise a kubevirtci tag mismatch can cause failures once running OVS e2e tests from CNAO.

Beside that fix go download, as the previous method doesn't work anymore.
https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/k8snetworkplumbingwg_ovs-cni/319/pull-e2e-ovs-cni/1808463231954456576#1:build-log.txt%3A9859

go.mod was changed to fit the new download mechanism,
but anyhow lately this is common on all repos to add the patch, i.e kubevirt as well
that was changed lately https://github.com/kubevirt/kubevirt/blob/a3b2bf3a54936b3dedf1341f6927ba6bdda51557/go.mod#L210
This semantic is allowed, and even required when the toolchain arg will present.

Special notes for your reviewer:

Release note:

None

@kubevirt-bot
Copy link
Collaborator

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kubevirt-bot kubevirt-bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. labels Jul 3, 2024
It is helpful either manually or for example
when used from CNAO, to use same tag of the cluster that CNAO deployed.
Otherwise a kubevirtci tag mismatch can cause failures once running from CNAO.

Signed-off-by: Or Shoval <oshoval@redhat.com>
@oshoval oshoval changed the title WIP Allow kubevirtci tag overriding cluster: Allow kubevirtci tag overriding Jul 3, 2024
@oshoval oshoval marked this pull request as ready for review July 3, 2024 11:30
@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. labels Jul 3, 2024
Previous method doesnt support newer versions anymore
(or not at least atm).

Just use wget instead.

Signed-off-by: Or Shoval <oshoval@redhat.com>
@phoracek
Copy link
Member

phoracek commented Jul 3, 2024

/lgtm
/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jul 3, 2024
@kubevirt-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: oshoval, phoracek

The full list of commands accepted by this bot can be found here.

The pull request process is described here

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 3, 2024
@kubevirt-bot kubevirt-bot merged commit 067f77c into k8snetworkplumbingwg:main Jul 3, 2024
5 checks passed
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. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants