Skip to content

Conversation

akalenyu
Copy link
Collaborator

@akalenyu akalenyu commented Jul 1, 2025

What this PR does / why we need it:
We (think) that it's possible for a Bound PVC
post rebind to briefly have a garbage capacity value,
which could break cloning via automated workflows.

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:

NONE

We (think) that it's possible for a Bound PVC
post rebind to briefly have a garbage capacity value,
which could break cloning via automated workflows.

Signed-off-by: Alex Kalenyuk <[email protected]>
@kubevirt-bot kubevirt-bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. dco-signoff: yes Indicates the PR's author has DCO signed all their commits. labels Jul 1, 2025
@kubevirt-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@akalenyu
Copy link
Collaborator Author

akalenyu commented Jul 1, 2025

/test all

@kubevirt-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign awels for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@coveralls
Copy link

coveralls commented Jul 1, 2025

Coverage Status

coverage: 59.392% (+0.04%) from 59.348%
when pulling 7394f92 on akalenyu:rebind-capacity-present
into d4a959a on kubevirt:main.

@akalenyu
Copy link
Collaborator Author

akalenyu commented Jul 3, 2025

/test all

1 similar comment
@akalenyu
Copy link
Collaborator Author

akalenyu commented Jul 3, 2025

/test all

@kubevirt-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@kubevirt-bot kubevirt-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dco-signoff: yes Indicates the PR's author has DCO signed all their commits. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. release-note-none Denotes a PR that doesn't merit a release note. size/M

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants