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
core: Preallocate blank block volumes #1559
core: Preallocate blank block volumes #1559
Conversation
Importer pod needs to be started for blank block volumes and it needs to handle the case. Signed-off-by: Tomasz Baranski <tbaransk@redhat.com>
/retest |
Sorry to be asking this question rather late -- why do we want to preallocate block disks? |
OK, I can answer my own question: because if someone asks for preallocation it's surprising if it doesn't do that in some scenarios. |
Skip("Storage Class for block volume is not available") | ||
} | ||
|
||
return utils.NewDataVolumeForBlankRawImageBlock("import-dv", "100Mi", f.BlockSCName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A full alloc should be pretty slow, so there should be enough time to verify that a pod actually was created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default 270 seconds should be enough for anybod^W writing 100Mi of zeros.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well the new part here is that for a block device we DO create a pod if preallocation is set to true. So our test should actually verify the pod is created.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The test verifies that the preallocation annotation has been created, and it's only created when the pod started AND finished successfully.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha, didn't realize the annotation was created only if the pod started and finished.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[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 |
/cherry-pick release-v1.28 |
@tomob: #1559 failed to apply on top of branch "release-v1.28":
In response to this:
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. |
Importer pod needs to be started for blank block volumes and it needs to handle the case. Signed-off-by: Tomasz Baranski <tbaransk@redhat.com>
Importer pod needs to be started for blank block volumes and it needs to handle the case. Signed-off-by: Tomasz Baranski <tbaransk@redhat.com> Signed-off-by: Tomasz Barański <tomob@users.noreply.github.com>
Importer pod needs to be started for blank block volumes and it needs to handle the case. Signed-off-by: Tomasz Baranski <tbaransk@redhat.com>
Signed-off-by: Tomasz Baranski tbaransk@redhat.com
What this PR does / why we need it:
Importer pod needs to be started for blank block volumes and it needs to
handle the case.
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: