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

Fix for hotplug with WFFC and CDI populators + test fixes #9918

Merged
merged 2 commits into from Jun 16, 2023

Conversation

ShellyKa13
Copy link
Contributor

What this PR does / why we need it:
When Kubevirt will run with newer version of CDI with integration of data volumes and CDI populators DV with WFFC SCI storage class will have new phase pendingPopulation, when hotpluging a dv with this phase we can continue to create the attachment pod and it will trigger the population.
This PR fixes the check if a dv is ready to be attached.
Also adjusting some tests to take into account either WFFC phase or PendingPopulation phase.

Release note:

Fix for hotplug with WFFC SCI storage class which uses CDI populators

When dv uses cdi populators it doesn't need
a doppelganger pod for wffc storage class
it can be attached and then it will get populated.
Fix missing condition in case dv phase is pendingPopulation
you can trigger the attachment pod.

Signed-off-by: Shelly Kagan <skagan@redhat.com>
When having WFFC storage class if this is a sci storage class
cdi populators will be used and dv will have new phase:
PendingPopulation, expect the phase to be either WFFC or that.

Signed-off-by: Shelly Kagan <skagan@redhat.com>
@kubevirt-bot kubevirt-bot added release-note Denotes a PR that will be considered when it comes time to generate release notes. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jun 15, 2023
@mhenriks
Copy link
Member

/lgtm
/approve

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Jun 15, 2023
@kubevirt-bot
Copy link
Contributor

[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 Jun 15, 2023
@mhenriks
Copy link
Member

/cherry-pick release-1.0

@kubevirt-bot
Copy link
Contributor

@mhenriks: once the present PR merges, I will cherry-pick it on top of release-1.0 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.0

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.

@kubevirt-bot kubevirt-bot merged commit 3fad00e into kubevirt:main Jun 16, 2023
35 checks passed
@kubevirt-bot
Copy link
Contributor

@mhenriks: new pull request created: #9931

In response to this:

/cherry-pick release-1.0

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. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/S
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants