Skip to content
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: fix mapOptions passing with rbd-nbd mounter #2636

Merged
merged 3 commits into from
Nov 16, 2021
Merged

Conversation

pkalever
Copy link

@pkalever pkalever commented Nov 14, 2021

Describe what this PR does

Signed-off-by: Prasanna Kumar Kalever prasanna.kalever@redhat.com

Fixes: #2610.
Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>


Show available bot commands

These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

  • /retest ci/centos/<job-name>: retest the <job-name> after unrelated
    failure (please report the failure too!)
  • /retest all: run this in case the CentOS CI failed to start/report any test
    progress or results

This got removed unintentionally with
ceph#2628

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
@mergify mergify bot added component/rbd Issues related to RBD bug Something isn't working labels Nov 14, 2021
@pkalever pkalever requested review from nixpanic, Madhu-1 and a team November 14, 2021 09:11
@pkalever
Copy link
Author

All the tests are hitting a different common issue:

https://jenkins-ceph-csi.apps.ocp.ci.centos.org/job/mini-e2e-helm_k8s-1.20/3078/display/redirect
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/job/mini-e2e-helm_k8s-1.21/1737/display/redirect
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/job/mini-e2e-helm_k8s-1.22/1027/display/redirect

https://jenkins-ceph-csi.apps.ocp.ci.centos.org/job/mini-e2e_k8s-1.20/3096/display/redirect
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/job/mini-e2e_k8s-1.21/1753/display/redirect
https://jenkins-ceph-csi.apps.ocp.ci.centos.org/job/mini-e2e_k8s-1.22/1004/display/redirect

�[1mSTEP�[0m: create a PVC and bind it to an app using rbd-nbd mounter with encryption
Nov 14 09:47:49.419: INFO: waiting for kubectl (delete -f args []) to finish
Nov 14 09:47:49.419: INFO: Running '/usr/bin/kubectl --server=https://192.168.39.54:8443 --kubeconfig=/root/.kube/config --namespace=cephcsi-e2e-2ea9e9c277d7 delete -f -'
Nov 14 09:47:49.491: INFO: stderr: "warning: deleting cluster-scoped resources, not scoped to the provided namespace\n"
Nov 14 09:47:49.491: INFO: stdout: "storageclass.storage.k8s.io \"csi-rbd-sc\" deleted\n"
Nov 14 09:47:49.496: INFO: ExecWithOptions {Command:[/bin/sh -c ceph fsid] Namespace:rook-ceph PodName:rook-ceph-tools-7467d8bf8-wjvdf ContainerName:rook-ceph-tools Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Nov 14 09:47:49.496: INFO: >>> kubeConfig: /root/.kube/config
Nov 14 09:47:50.414: INFO: Waiting up to &PersistentVolumeClaim{ObjectMeta:{rbd-pvc  rbd-1318    0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*csi-rbd-sc,VolumeMode:nil,DataSource:nil,DataSourceRef:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},} to be in Bound state
Nov 14 09:47:50.414: INFO: waiting for PVC rbd-pvc (0 seconds elapsed)
Nov 14 09:47:52.417: INFO: waiting for PVC rbd-pvc (2 seconds elapsed)
Nov 14 09:47:52.421: INFO: Waiting for PV pvc-427711d5-35cc-4e42-a0a1-b2097903c783 to bind to PVC rbd-pvc
Nov 14 09:47:52.421: INFO: Waiting up to timeout=10m0s for PersistentVolumeClaims [rbd-pvc] to have phase Bound
Nov 14 09:47:52.423: INFO: PersistentVolumeClaim rbd-pvc found and phase=Bound (1.923219ms)
Nov 14 09:47:52.423: INFO: Waiting up to 10m0s for PersistentVolume pvc-427711d5-35cc-4e42-a0a1-b2097903c783 to have phase Bound
Nov 14 09:47:52.425: INFO: PersistentVolume pvc-427711d5-35cc-4e42-a0a1-b2097903c783 found and phase=Bound (2.076567ms)
Nov 14 09:47:52.432: INFO: Waiting up to csi-rbd-demo-pod to be in Running state
Nov 14 09:48:20.444: INFO: ExecWithOptions {Command:[/bin/sh -c rbd image-meta get replicapool/csi-vol-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 rbd.csi.ceph.com/encrypted] Namespace:rook-ceph PodName:rook-ceph-tools-7467d8bf8-wjvdf ContainerName:rook-ceph-tools Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Nov 14 09:48:20.444: INFO: >>> kubeConfig: /root/.kube/config
Nov 14 09:48:20.839: INFO: ExecWithOptions {Command:[/bin/sh -c lsblk -o TYPE,MOUNTPOINT | grep '/var/lib/www/html' | awk '{print $1}'] Namespace:rbd-1318 PodName:csi-rbd-demo-pod ContainerName:web-server Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Nov 14 09:48:20.839: INFO: >>> kubeConfig: /root/.kube/config
Nov 14 09:48:20.932: FAIL: failed to validate encrypted pvc with error  not equal to crypt

nodeplugin logs:

I1114 09:48:09.587996   36302 cephcmds.go:62] ID: 7 Req-ID: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 command succeeded: rbd [--id cephcsi-rbd-node -m rook-ceph-mon-a.rook-ceph.svc.cluster.local:6789 --keyfile=***stripped*** --log-file /var/log/ceph/rbd-nbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26.log map replicapool/csi-vol-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 --device-type nbd --options try-netlink --options reattach-timeout=300 --options debug-rbd=20,io-timeout=330]
I1114 09:48:09.588031   36302 nodeserver.go:401] ID: 7 Req-ID: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 rbd image: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26/replicapool was successfully mapped at /dev/nbd0
I1114 09:48:09.604305   36302 encryption.go:80] ID: 7 Req-ID: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 image replicapool/csi-vol-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 encrypted state metadata reports "encryptionPrepared"
I1114 09:48:09.604346   36302 mount_linux.go:463] Attempting to determine if disk "/dev/nbd0" is formatted using blkid with args: ([-p -s TYPE -s PTTYPE -o export /dev/nbd0])
I1114 09:48:09.606317   36302 mount_linux.go:466] Output: ""
I1114 09:48:09.606363   36302 crypto.go:199] ID: 7 Req-ID: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 Encrypting device /dev/nbd0 with LUKS
I1114 09:48:15.444350   36302 crypto.go:254] ID: 7 Req-ID: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 device /dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 is not an active LUKS device: an error (exit status 4) occurred while running cryptsetup args: [status luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26]
I1114 09:48:15.444391   36302 crypto.go:209] ID: 7 Req-ID: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 Opening device /dev/nbd0 with LUKS on luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26
I1114 09:48:17.189119   36302 mount_linux.go:463] Attempting to determine if disk "/dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26" is formatted using blkid with args: ([-p -s TYPE -s PTTYPE -o export /dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26])
I1114 09:48:17.217169   36302 mount_linux.go:466] Output: ""
I1114 09:48:17.319419   36302 mount_linux.go:463] Attempting to determine if disk "/dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26" is formatted using blkid with args: ([-p -s TYPE -s PTTYPE -o export /dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26])
I1114 09:48:17.352173   36302 mount_linux.go:466] Output: "DEVNAME=/dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26\nTYPE=ext4\n"
I1114 09:48:17.352223   36302 mount_linux.go:357] Checking for issues with fsck on disk: /dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26
I1114 09:48:17.418496   36302 mount_linux.go:453] Attempting to mount disk /dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 in ext4 format at /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-427711d5-35cc-4e42-a0a1-b2097903c783/globalmount/0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26
I1114 09:48:17.418561   36302 mount_linux.go:180] Mounting cmd (mount) with arguments (-t ext4 -o _netdev,discard,defaults /dev/mapper/luks-rbd-0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-427711d5-35cc-4e42-a0a1-b2097903c783/globalmount/0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26)
I1114 09:48:17.430089   36302 nodeserver.go:361] ID: 7 Req-ID: 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 rbd: successfully mounted volume 0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26 to stagingTargetPath /var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-427711d5-35cc-4e42-a0a1-b2097903c783/globalmount/0001-0024-cfb024e1-4eee-4917-b9ec-8acb0f4afcb8-0000000000000001-ee3d6f50-452f-11ec-8fc8-9acf4e9aad26

Which is different from what we have seen before!

@pkalever
Copy link
Author

@ceph/ceph-csi-contributors I have reordered the e2e tests in a way that krbd encryption tests runs first, just to prove that the bug is not nbd specific. See latest CI results.

I guess we introduced yet another regression in encryption. Anyone know about it?

@pkalever pkalever added the DNM DO NOT MERGE label Nov 14, 2021
@Madhu-1
Copy link
Collaborator

Madhu-1 commented Nov 15, 2021

I have reordered the e2e tests in a way that krbd encryption tests runs first, just to prove that the bug is not nbd specific. See latest CI results.

I guess we introduced yet another regression in encryption. Anyone know about it?

but why the E2E is failing only for nbd? can we open a PR to disable nbd and test encryption with krbd to verify the regression?

@pkalever
Copy link
Author

I have reordered the e2e tests in a way that krbd encryption tests runs first, just to prove that the bug is not nbd specific. See latest CI results.
I guess we introduced yet another regression in encryption. Anyone know about it?

but why the E2E is failing only for nbd? can we open a PR to disable nbd and test encryption with krbd to verify the regression?

@Madhu-1 sorry, I didn't get you.
Have you missed seeing that the latest e2e tests are failing at test create a PVC and bind it to an app with encrypted RBD volume which is not NBD specific and uses krbd mounter only!

�[1mSTEP�[0m: create a PVC and bind it to an app with encrypted RBD volume
Nov 14 11:37:04.267: INFO: waiting for kubectl (delete -f args []) to finish
Nov 14 11:37:04.267: INFO: Running '/usr/bin/kubectl --server=https://192.168.39.7:8443 --kubeconfig=/root/.kube/config --namespace=cephcsi-e2e-8b66e001383f delete -f -'
Nov 14 11:37:04.341: INFO: stderr: "warning: deleting cluster-scoped resources, not scoped to the provided namespace\n"
Nov 14 11:37:04.341: INFO: stdout: "storageclass.storage.k8s.io \"csi-rbd-sc\" deleted\n"
Nov 14 11:37:04.345: INFO: ExecWithOptions {Command:[/bin/sh -c ceph fsid] Namespace:rook-ceph PodName:rook-ceph-tools-7467d8bf8-62zvp ContainerName:rook-ceph-tools Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Nov 14 11:37:04.345: INFO: >>> kubeConfig: /root/.kube/config
Nov 14 11:37:05.259: INFO: Waiting up to &PersistentVolumeClaim{ObjectMeta:{rbd-pvc  rbd-1318    0 0001-01-01 00:00:00 +0000 UTC <nil> <nil> map[] map[] [] []  []},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:*csi-rbd-sc,VolumeMode:nil,DataSource:nil,DataSourceRef:nil,},Status:PersistentVolumeClaimStatus{Phase:,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},} to be in Bound state
Nov 14 11:37:05.259: INFO: waiting for PVC rbd-pvc (0 seconds elapsed)
Nov 14 11:37:07.262: INFO: waiting for PVC rbd-pvc (2 seconds elapsed)
Nov 14 11:37:07.267: INFO: Waiting for PV pvc-a2efc7e6-68f3-422c-99f2-8bb2ac2eb070 to bind to PVC rbd-pvc
Nov 14 11:37:07.267: INFO: Waiting up to timeout=10m0s for PersistentVolumeClaims [rbd-pvc] to have phase Bound
Nov 14 11:37:07.269: INFO: PersistentVolumeClaim rbd-pvc found and phase=Bound (1.862348ms)
Nov 14 11:37:07.269: INFO: Waiting up to 10m0s for PersistentVolume pvc-a2efc7e6-68f3-422c-99f2-8bb2ac2eb070 to have phase Bound
Nov 14 11:37:07.270: INFO: PersistentVolume pvc-a2efc7e6-68f3-422c-99f2-8bb2ac2eb070 found and phase=Bound (1.769751ms)
Nov 14 11:37:07.278: INFO: Waiting up to csi-rbd-demo-pod to be in Running state
Nov 14 11:37:25.290: INFO: ExecWithOptions {Command:[/bin/sh -c rbd image-meta get replicapool/csi-vol-313c62e6-453f-11ec-81bd-12cf8b4b9b0f rbd.csi.ceph.com/encrypted] Namespace:rook-ceph PodName:rook-ceph-tools-7467d8bf8-62zvp ContainerName:rook-ceph-tools Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Nov 14 11:37:25.290: INFO: >>> kubeConfig: /root/.kube/config
Nov 14 11:37:25.687: INFO: ExecWithOptions {Command:[/bin/sh -c lsblk -o TYPE,MOUNTPOINT | grep '/var/lib/www/html' | awk '{print $1}'] Namespace:rbd-1318 PodName:csi-rbd-demo-pod ContainerName:web-server Stdin:<nil> CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Nov 14 11:37:25.687: INFO: >>> kubeConfig: /root/.kube/config
Nov 14 11:37:25.816: FAIL: failed to validate encrypted pvc with error  not equal to crypt

@pkalever
Copy link
Author

@ceph/ceph-csi-contributors

I don't know why but the mount type is empty instead of crypt, hence it is failing exactly at https://github.com/ceph/ceph-csi/blob/devel/e2e/rbd_helper.go#L556

Have we seen this before? Or has anyone made changes recently in this code path?

Copy link
Collaborator

@Madhu-1 Madhu-1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. as the tests are even failing on krbd commit 3 can be removed?

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Nov 15, 2021

@pkalever is this test failing manually also if we try 3/4 times?

@Madhu-1 I have tried it locally and checked manually, the pod comes up clean with NBD + encryption with this changes (unlike before)

@pkalever
Copy link
Author

LGTM. as the tests are even failing on krbd commit 3 can be removed?

Yes, certainly!

@pkalever pkalever requested a review from Madhu-1 November 15, 2021 09:44
@pkalever pkalever removed the DNM DO NOT MERGE label Nov 15, 2021
@pkalever
Copy link
Author

/retest ci/centos/mini-e2e/k8s-1.22

X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

@nixpanic
Copy link
Member

Nov 14 11:37:25.687: INFO: ExecWithOptions {Command:[/bin/sh -c lsblk -o TYPE,MOUNTPOINT | grep '/var/lib/www/html' | awk '{print $1}'] Namespace:rbd-1318 PodName:csi-rbd-demo-pod ContainerName:web-server Stdin: CaptureStdout:true CaptureStderr:true PreserveWhitespace:true Quiet:false}
Nov 14 11:37:25.687: INFO: >>> kubeConfig: /root/.kube/config
Nov 14 11:37:25.816: FAIL: failed to validate encrypted pvc with error not equal to crypt

This test should run on the nodeplugin, not inside the application pod... The application may not see, or have sufficient permissions for detecting the block-device type (encrypted or not).

@pkalever
Copy link
Author

This test should run on the nodeplugin, not inside the application pod... The application may not see, or have sufficient permissions for detecting the block-device type (encrypted or not).

@nixpanic
Sure, refreshed with the required changes. Thanks!

@pkalever
Copy link
Author

/retest ci/centos/mini-e2e-helm/k8s-1.20

X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

e2e/rbd_helper.go Outdated Show resolved Hide resolved
e2e/rbd_helper.go Outdated Show resolved Hide resolved
@pkalever pkalever force-pushed the fix-2610 branch 2 times, most recently from 425d1ea to 089d34b Compare November 15, 2021 17:51
@mergify mergify bot dismissed stale reviews from Rakshith-R and Madhu-1 November 16, 2021 07:47

Pull request has been modified.

@Madhu-1 Madhu-1 requested a review from Rakshith-R November 16, 2021 07:50
@pkalever
Copy link
Author

/retest ci/centos/k8s-e2e-external-storage/1.22
/retest ci/centos/mini-e2e-helm/k8s-1.22

X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute

@mergify mergify bot merged commit 0bf9db8 into ceph:devel Nov 16, 2021
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 16, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 16, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 16, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 16, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 16, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 17, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 17, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 18, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 18, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 18, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 18, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 18, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 18, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 22, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
pkalever pushed a commit to pkalever/ceph-csi that referenced this pull request Nov 23, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
ceph#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
mergify bot pushed a commit that referenced this pull request Nov 23, 2021
Uses the below schema to supply mounter specific map/unmapOptions to the
nodeplugin based on the discussion we all had at
#2636

This should specifically be really helpful with the `tryOthermonters`
set to true, i.e with fallback mechanism settings turned ON.

mapOption: "kbrd:v1,v2,v3;nbd:v1,v2,v3"

- By omitting `krbd:` or `nbd:`, the option(s) apply to
  rbdDefaultMounter which is krbd.
- A user can _override_ the options for a mounter by specifying `krbd:`
  or `nbd:`.
  mapOption: "v1,v2,v3;nbd:v1,v2,v3"
  is effectively the same as the 1st example.
- Sections are split by `;`.
- If users want to specify common options for both `krbd` and `nbd`,
  they should mention them twice.

Signed-off-by: Prasanna Kumar Kalever <prasanna.kalever@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working component/rbd Issues related to RBD
Projects
None yet
Development

Successfully merging this pull request may close these issues.

rbd-nbd: failed to validate encrypted pvc with error timed out waiting for the condition
6 participants