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-up: Fix tag updating #2189

Merged
merged 1 commit into from
Dec 22, 2022
Merged

Conversation

oshoval
Copy link
Contributor

@oshoval oshoval commented Dec 21, 2022

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

Reviewers are supposed to review the PR for every aspect below one by one. To check an item means the PR is either "OK" or "Not Applicable" in terms of that item. All items are supposed to be checked before merging a PR.

  • PR Message
  • Commit Messages
  • How to test
  • Unit Tests
  • Functional Tests
  • User Documentation
  • Developer Documentation
  • Upgrade Scenario
  • Uninstallation Scenario
  • Backward Compatibility
  • Troubleshooting Friendly

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 Dec 21, 2022
@oshoval
Copy link
Contributor Author

oshoval commented Dec 21, 2022

/cc @tiraboschi @orenc1

@coveralls
Copy link
Collaborator

coveralls commented Dec 21, 2022

Pull Request Test Coverage Report for Build 3757146658

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 85.599%

Totals Coverage Status
Change from base Build 3735078185: 0.0%
Covered Lines: 4684
Relevant Lines: 5472

💛 - Coveralls

cluster/kubevirtci.sh Outdated Show resolved Hide resolved
@nunnatsa
Copy link
Collaborator

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]>
@oshoval
Copy link
Contributor Author

oshoval commented Dec 22, 2022

Thanks
Addressed comments

@sonarqubecloud
Copy link

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

Copy link
Collaborator

@nunnatsa nunnatsa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Dec 22, 2022
@kubevirt-bot
Copy link
Contributor

[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 /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 Dec 22, 2022
@kubevirt-bot kubevirt-bot merged commit a0a3627 into kubevirt:main Dec 22, 2022
tiraboschi pushed a commit to tiraboschi/hyperconverged-cluster-operator that referenced this pull request Mar 14, 2023
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]>
kubevirt-bot pushed a commit that referenced this pull request Mar 20, 2023
* [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]>
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/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants