Skip to content

cluster: Fix kubevirtci clone storm#98

Merged
kubevirt-bot merged 1 commit intokubevirt:mainfrom
oshoval:cluster-up-fix
Mar 23, 2026
Merged

cluster: Fix kubevirtci clone storm#98
kubevirt-bot merged 1 commit intokubevirt:mainfrom
oshoval:cluster-up-fix

Conversation

@oshoval
Copy link
Copy Markdown
Collaborator

@oshoval oshoval commented Mar 10, 2026

What this PR does / why we need it:

cluster::install checks whether the existing kubevirtci clone matches the requested one by comparing both the remote URL and the tag.
The remote URL check fails when the clone was done via SSH (git@github.com:...) because the stored KUBEVIRTCI_REPO uses HTTPS (https://github.com/...).
The mismatch causes kubevirtci to be deleted and re-cloned on every invocation, wiping the cluster kubeconfig and breaking the dev workflow.

Remove the remote URL check and keep only the tag comparison.

Derived from: kubevirt/cluster-network-addons-operator#2619

Special notes for your reviewer:

Release note:

NONE

@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Mar 10, 2026
@kubevirt-bot kubevirt-bot requested review from phoracek and qinqon March 10, 2026 14:37
@oshoval
Copy link
Copy Markdown
Collaborator Author

oshoval commented Mar 10, 2026

cc @ormergi

cluster::install checks whether the existing kubevirtci clone matches
the requested one by comparing both the remote URL and the tag.

The remote URL check fails when the clone was done via SSH
(git@github.com:...) because the stored KUBEVIRTCI_REPO uses HTTPS
(https://github.com/...). The mismatch causes kubevirtci to be deleted
and re-cloned on every invocation, wiping the cluster kubeconfig and
breaking the dev workflow.

Remove the remote URL check and keep only the tag comparison.
Drop the now-unused KUBEVIRTCI_REPO variable.

Derived from: kubevirt/cluster-network-addons-operator#2619
Assisted-by: Cursor (claude-4.6-sonnet-medium-thinking)
Signed-off-by: Or Shoval <oshoval@redhat.com>
@oshoval
Copy link
Copy Markdown
Collaborator Author

oshoval commented Mar 10, 2026

/retest

@ormergi
Copy link
Copy Markdown

ormergi commented Mar 10, 2026

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2026
@oshoval
Copy link
Copy Markdown
Collaborator Author

oshoval commented Mar 12, 2026

Thanks Or

@RamLavi can you please review ?

@kubevirt-bot
Copy link
Copy Markdown

Pull requests that are marked with lgtm should receive a review
from an approver within 1 week.

After that period the bot marks them with the label needs-approver-review.

/label needs-approver-review

@kubevirt-bot kubevirt-bot added the needs-approver-review Indicates that a PR requires a review from an approver. label Mar 19, 2026
@qinqon
Copy link
Copy Markdown
Contributor

qinqon commented Mar 23, 2026

/lgtm
/approve

@kubevirt-bot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qinqon

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

@kubevirt-bot kubevirt-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 23, 2026
@kubevirt-bot kubevirt-bot merged commit 45ff79b into kubevirt:main Mar 23, 2026
4 checks passed
@kubevirt-bot
Copy link
Copy Markdown

/remove-label needs-approver-review

@kubevirt-bot kubevirt-bot removed the needs-approver-review Indicates that a PR requires a review from an approver. label Mar 23, 2026
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. size/XS

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants