-
Notifications
You must be signed in to change notification settings - Fork 807
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 the bug by passing fstype correctly #335
Conversation
@leakingtapan: GitHub didn't allow me to request PR reviews from the following users: shanesiebken. Note that only kubernetes-sigs members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: leakingtapan 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 |
Pull Request Test Coverage Report for Build 750
💛 - Coveralls |
90ec455
to
a4e37c0
Compare
/retest |
/retest |
/lgtm |
something wrong with coveralls https://status.coveralls.io/ we use in travis |
/retest |
I notice removing the |
1. Fix fstype parameter prefix 2. Remove fstype in storageclass in favor of csi.storage.k8s.io/fstype 3. Update e2e test 4. Add static provisioning example 5. Update run-e2e-test script to build driver before create cluster
VolumeContext: map[string]string{ | ||
FsTypeKey: disk.FsType, | ||
}, | ||
VolumeContext: map[string]string{}, |
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.
OK: external-provisioner will fill in volume.spec.csi.fstype for us
/lgtm re-adding |
merged manually since the coverage drop is due to the deprecation message added |
Is this a bug fix or adding new feature?
Fixes: #324 #326
/cc @wongma7 @jsafrane @shanesiebken
What is this PR about? / Why do we need it?
This fixes a bug to use
fstype
inside volume capacity for NodeStageVolume and NodePublishVolume call. So that pre-created persistence volume's fstype is used when mounting the volume correctly.This change also removed the usage of
fstype
in driver's storage class parameter in favor of reservedcsi.storage.k8s.io/fstype
parameter.What testing is done?
Tested on Kops cluster with a pre-created xfs EBS volume and consume it with
fstype
set in the PV spec.