-
Notifications
You must be signed in to change notification settings - Fork 547
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
rbd: consider rbd as default mounter if not set. (backport #3080) #3107
Conversation
Looks like we need #3102 backport to release-3.6 branch also |
commitlint is failing with above error message. |
@Mergifyio rebase |
For the default mounter the mounter option will not be set in the storageclass and as it is not available in the storageclass same will not be set in the volume context, Because of this the mapOptions are getting discarded. If the mounter is not set assuming it's an rbd mounter. Note:- If the mounter is not set in the storageclass we can set it in the volume context explicitly, Doing this check-in node server to support backward existing volumes and the check is minimal we are not altering the volume context. fixes: #3076 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com> (cherry picked from commit 7067456)
✅ Branch has been successfully rebased |
1a70fa5
to
27bc30c
Compare
/retest ci/centos/mini-e2e-helm/k8s-1.21 |
/retest ci/centos/mini-e2e-helm/k8s-1.23 |
@Mergifyio requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
/retest ci/centos/mini-e2e-helm/k8s-1.23 |
@Mergifyio requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
/retest ci/centos/mini-e2e-helm/k8s-1.21 |
@Mergifyio requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
/retest ci/centos/mini-e2e-helm/k8s-1.23 |
@Mergifyio requeue |
❌ This pull request head commit has not been previously disembarked from queue. |
This is an automatic backport of pull request #3080 done by Mergify.
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refresh
will re-evaluate the rules@Mergifyio rebase
will rebase this PR on its base branch@Mergifyio update
will merge the base branch into this PR@Mergifyio backport <destination>
will backport this PR on<destination>
branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com