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

[release-v1.49] Manual fix for clone without source pvc but target pvc already populated #2406

Conversation

ShellyKa13
Copy link
Contributor

What this PR does / why we need it:
This PR takes part of PR: #2306
and PR: #2375
to fix this issue with minimal changes.
In case the target pvc exists and populated we should allow the clone to complete successfully without doing anything

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 # BZ #2109407
https://bugzilla.redhat.com/show_bug.cgi?id=2109407
Special notes for your reviewer:

Release note:

Fix for clone without source pvc but target pvc already populated

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. size/L labels Aug 22, 2022
@ShellyKa13 ShellyKa13 force-pushed the clone-of-populated-pvc-release-v1.49 branch from 3895f3c to 577b6fa Compare August 22, 2022 13:46
In case the target pvc exists and populated we should allow the clone
to complete successfully without doing anything.
Adjust the code and add a test for that case.

Signed-off-by: Shelly Kagan <skagan@redhat.com>
@ShellyKa13 ShellyKa13 force-pushed the clone-of-populated-pvc-release-v1.49 branch from 577b6fa to b7cf62e Compare August 22, 2022 13:53
@mhenriks
Copy link
Member

/hold

@kubevirt-bot kubevirt-bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 25, 2022
@brybacki
Copy link
Contributor

@ShellyKa13 I think you need to coordinnate your change with @alromeros. If #2366 is merged, then your change could be smaller and simpler.

@mhenriks
Copy link
Member

/approve

@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 Aug 29, 2022
@brybacki
Copy link
Contributor

/lgtm

@kubevirt-bot kubevirt-bot added the lgtm Indicates that a PR is ready to be merged. label Aug 29, 2022
@ShellyKa13
Copy link
Contributor Author

/unhold

@kubevirt-bot kubevirt-bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 29, 2022
@kubevirt-bot kubevirt-bot merged commit b03e908 into kubevirt:release-v1.49 Aug 29, 2022
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/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants