-
Notifications
You must be signed in to change notification settings - Fork 261
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 uploading for block devices that exceed requested size #3461
Merged
kubevirt-bot
merged 1 commit into
kubevirt:main
from
kvaps:fix-check-size-for-block-devices
Oct 16, 2024
Merged
Fix uploading for block devices that exceed requested size #3461
kubevirt-bot
merged 1 commit into
kubevirt:main
from
kvaps:fix-check-size-for-block-devices
Oct 16, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kubevirt-bot
added
dco-signoff: no
Indicates the PR's author has not DCO signed all their commits.
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
size/S
labels
Oct 14, 2024
kvaps
force-pushed
the
fix-check-size-for-block-devices
branch
2 times, most recently
from
October 14, 2024 10:41
c90ef04
to
47c361e
Compare
kubevirt-bot
added
dco-signoff: yes
Indicates the PR's author has DCO signed all their commits.
release-note
Denotes a PR that will be considered when it comes time to generate release notes.
and removed
dco-signoff: no
Indicates the PR's author has not DCO signed all their commits.
do-not-merge/release-note-label-needed
Indicates that a PR should not merge because it's missing one of the release note labels.
labels
Oct 14, 2024
kvaps
force-pushed
the
fix-check-size-for-block-devices
branch
from
October 14, 2024 14:20
47c361e
to
9c19512
Compare
kvaps
changed the title
Fix: checking available image size for block volumes
Fix uploading for block devices that exceed requested size in PVC
Oct 14, 2024
kvaps
force-pushed
the
fix-check-size-for-block-devices
branch
from
October 14, 2024 15:27
9c19512
to
15d8a4e
Compare
kvaps
changed the title
Fix uploading for block devices that exceed requested size in PVC
Fix uploading for block devices that exceed requested size
Oct 14, 2024
/assign @awels |
This was referenced Oct 14, 2024
kvaps
force-pushed
the
fix-check-size-for-block-devices
branch
2 times, most recently
from
October 14, 2024 21:42
e633d9f
to
90fdd7f
Compare
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
kvaps
force-pushed
the
fix-check-size-for-block-devices
branch
from
October 14, 2024 22:21
90fdd7f
to
38e6d3c
Compare
/test pull-cdi-unit-test |
kvaps
added a commit
to aenix-io/cozystack
that referenced
this pull request
Oct 16, 2024
Upstream fix: kubevirt/containerized-data-importer#3461 Signed-off-by: Andrei Kvapil <kvapss@gmail.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Introduced a new version (`v1beta1`) for the CDI operator alongside the existing version, enhancing configuration options. - Expanded `spec` section with detailed descriptions for various configurations including data volume management and TLS security profiles. - Added a new Ingress resource for the `cdi-uploadproxy` service, improving traffic routing capabilities. - Introduced new configuration parameters for dynamic upload proxy URL management. - **Improvements** - Updated permissions for the CDI operator to manage additional resources, improving its data handling capabilities. - Refined deployment configuration with updated container image references and environment variables for better operational control. - Enhanced network policy definitions by adding specific rules for new services while maintaining existing policies. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: awels 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 |
kubevirt-bot
added
the
approved
Indicates a PR has been approved by an approver from all required OWNERS files.
label
Oct 16, 2024
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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Various storage providers may provision block devices larger than the size requested by the user. This is often due to LVM or ZFS rounding up to the nearest extent size. (see LINBIT/linstor-server#421 (comment) and #3159 (comment))
Currently, CDI checks the requested size in the PVC and fails the upload if the original block device is larger than the requested size.
This PR changes logic to take requestImageSize into account only for filesystem volumes
Which issue(s) this PR fixes:
Another try to fix #3159
Special notes for your reviewer:
Release note: