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

Test and env updates #208

Merged
merged 5 commits into from
Feb 1, 2024
Merged

Conversation

ShellyKa13
Copy link
Contributor

@ShellyKa13 ShellyKa13 commented Jan 15, 2024

What this PR does / why we need it:
This change is a first step in trying to make our tests usable to test compatibility with kubevirt for other backup partners.
This change marks tests that apply example manifests with label PartnerComp. This allows to run only those tests with gingko filter:
make TEST_ARGS="--test-args=-ginkgo.label-filter=PartnerComp" test-functional
Also those yamls were hardcoded with a storageclass, now changed the framework in order to make it possible to config other SC by updating env variable KVP_STORAGE_CLASS
To apply the yamls manually you'll need to replace the placeholder {{KVP_STORAGE_CLASS}} with your desired storageclass or run it with a replace command such as:
cat tests/manifests/vm_with_pvc.yaml | sed 's/{{KVP_STORAGE_CLASS}}/rook-ceph-block/g' | kubectl create -f -

Updated kubevirtci due to a bug in the last version of a problem running with docker.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

Special notes for your reviewer:

Release note:

Add PartnerComp label

@kubevirt-bot kubevirt-bot added the dco-signoff: yes Indicates the PR's author has DCO signed all their commits. label Jan 15, 2024
This label can be used to run tests with focus
on tests we consider neccessary to test partner
compatibility with kubevirt.
To run the tests:
make TEST_ARGS="--test-args=-ginkgo.label-filter=PartnerComp" test-functional

Signed-off-by: Shelly Kagan <skagan@redhat.com>
@@ -0,0 +1,201 @@
Apache License
Copy link
Member

Choose a reason for hiding this comment

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

Did you mean to add this dir?

Copy link
Contributor Author

@ShellyKa13 ShellyKa13 Jan 21, 2024

Choose a reason for hiding this comment

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

this was done automatically when running the update kubevirtci script..

Copy link
Member

Choose a reason for hiding this comment

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

Yeah at some point velero is downloaded but I don't think we want to add it to the repo. Maybe put something in gitignore?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@mhenriks add the gitignore and deleted an existing velero repo we had in here.

@mhenriks
Copy link
Member

@ShellyKa13 Can you edit the PR description to briefly state reasoning for changes to to tests/manifests?

This change allows the user to set env variable
KVP_STORAGE_CLASS with the desired storage class
one wants the tests applying yamls to run with.
Adjust some tests to pass when using wffc SC

Signed-off-by: Shelly Kagan <skagan@redhat.com>
The test wants to catch the dv in state importing
but if the import is fast we can miss it.
Insted we can check that a file that existed
no longer exists after the backup.

Signed-off-by: Shelly Kagan <skagan@redhat.com>
Signed-off-by: Shelly Kagan <skagan@redhat.com>
@ShellyKa13 ShellyKa13 force-pushed the test-and-env-updates branch 2 times, most recently from d171a45 to 39c8ad9 Compare January 30, 2024 15:46
Signed-off-by: Shelly Kagan <skagan@redhat.com>
@mhenriks
Copy link
Member

mhenriks commented Feb 1, 2024

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mhenriks

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 Feb 1, 2024
@kubevirt-bot kubevirt-bot merged commit 3bc1ff3 into kubevirt:main Feb 1, 2024
4 of 5 checks passed
@ShellyKa13
Copy link
Contributor Author

/cherrypick release-0.6

@kubevirt-bot
Copy link

@ShellyKa13: cannot checkout release-0.6: error checking out "release-0.6": exit status 1 error: pathspec 'release-0.6' did not match any file(s) known to git

In response to this:

/cherrypick release-0.6

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/test-infra repository.

@ShellyKa13
Copy link
Contributor Author

/cherrypick release-v0.6

@kubevirt-bot
Copy link

@ShellyKa13: new pull request created: #220

In response to this:

/cherrypick release-v0.6

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/test-infra repository.

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. size/XL
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants