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
Add volume capabilities validation in Vanilla Create Volume Request #459
Conversation
Make check:
Unit tests:
|
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.
/approve
jtest file-vanilla |
Started vanilla file pipeline... |
LGTM. Lets wait for successful vanilla test results. /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chethanv28, divyenpatel, SandeepPissay 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 |
jtest file-vanilla |
Started vanilla file pipeline... |
|
|
Started vanilla file pipeline... |
|
Started vanilla file pipeline... |
|
Started vanilla file pipeline... |
|
Started vanilla file pipeline... |
|
Started vanilla file pipeline... |
|
Started vanilla file pipeline... |
|
Started vanilla file pipeline... |
|
Started vanilla file pipeline... |
|
1 test failed because the test expects a generic error message. I have changed the test case to expect the exact error message reran the failed e2e test:
|
/lgtm |
What this PR does / why we need it:
This PR is adding a validation for create block volume request to avoid incorrect (SC - fstype : PVC- AccessMode) combination used in volume creation
For ex: Creating a block volume with fstype: nfs or nfs4
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: