-
Notifications
You must be signed in to change notification settings - Fork 153
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-up: Fix tag updating #2189
Conversation
/cc @tiraboschi @orenc1 |
Pull Request Test Coverage Report for Build 3757146658
💛 - Coveralls |
Thanks @oshoval - good catch! Added an optional nit comment. |
In case the _kubevirtci folder exists, changing the tag won't reclone the folder. The cluster-up folder won't be updated and it can lead to bugs in case the folder is changed. Fix it by deleting the folder in case of tag mismatch. It will enforce a reclone. Signed-off-by: Or Shoval <[email protected]>
Thanks |
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: nunnatsa 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 |
In case the _kubevirtci folder exists, changing the tag won't reclone the folder. The cluster-up folder won't be updated and it can lead to bugs in case the folder is changed. Fix it by deleting the folder in case of tag mismatch. It will enforce a reclone. Signed-off-by: Or Shoval <[email protected]> Signed-off-by: Or Shoval <[email protected]>
* [release-1.8] Align github actions from newer branches Backport a few configuration changes in github actions. Signed-off-by: stirabos <[email protected]> * Fix bug and change cri selection procedure of cluster-sync. (#2155) The command for getting the registry port gets more than one output, which breaks following commands in the deploying scripts. The output is now parsed to pickup just the first port. Also the container runtime selection was hardcoded, now it uses the cri selection script of kubervirtci. Co-authored-by: Felix Matouschek <[email protected]> Signed-off-by: Javier Cano Cano <[email protected]> Signed-off-by: Javier Cano Cano <[email protected]> Co-authored-by: Felix Matouschek <[email protected]> * cluster-up: Fix tag updating (#2189) In case the _kubevirtci folder exists, changing the tag won't reclone the folder. The cluster-up folder won't be updated and it can lead to bugs in case the folder is changed. Fix it by deleting the folder in case of tag mismatch. It will enforce a reclone. Signed-off-by: Or Shoval <[email protected]> Signed-off-by: Or Shoval <[email protected]> * Bump the default kubevirtci provider Signed-off-by: stirabos <[email protected]> * Workaround for SELinux boolean for chardev Workaround for kubevirt/kubevirt#9434 we started setting SELinux boolean for chardev access with kubevirt/kubevirtci#968 but it got reverted with kubevirt/kubevirtci#975 altough it's still needed with Kubevirt v0.58.1 TODO: let's remove this once kubevirt/kubevirt#9434 is fixed Signed-off-by: stirabos <[email protected]> --------- Signed-off-by: stirabos <[email protected]> Signed-off-by: Javier Cano Cano <[email protected]> Signed-off-by: Or Shoval <[email protected]> Co-authored-by: Javier Cano Cano <[email protected]> Co-authored-by: Felix Matouschek <[email protected]> Co-authored-by: oscollabus <[email protected]>
In case the _kubevirtci folder exists,
changing the tag won't reclone the folder.
The cluster-up folder won't be updated and it can lead to bugs in case the folder is changed.
Fix it by deleting the folder in case of tag mismatch.
It will enforce a reclone.
Reviewer Checklist
Release note: