-
Notifications
You must be signed in to change notification settings - Fork 453
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
Verify required checkpoint parameters are set #1263
Verify required checkpoint parameters are set #1263
Conversation
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.
Thanks!
/ok-to-test |
Without this change it was possible to run crictl checkpoint CTR-ID without specifying '--export'. The export parameter is, however, required as it tell the CRI implementation where to store the checkpoint archive. This commit adds a check to ensure '--export' is set and not empty. Signed-off-by: Adrian Reber <areber@redhat.com>
200f8ad
to
04fb3af
Compare
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: adrianreber, saschagrunert 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 |
What type of PR is this?
/kind bug
What this PR does / why we need it:
Without this change it was possible to run
without specifying '--export'. The export parameter is, however, required as it tell the CRI implementation where to store the checkpoint archive. This commit adds a check to ensure '--export' is set and not empty.
Which issue(s) this PR fixes:
Fixes #1235
Special notes for your reviewer:
Does this PR introduce a user-facing change?