If one defines the ibm.io/debug-level only as a storage-class property and not in as an attribute in the PVC, the created PV will set the ibm.io/debug-level attribute to nil, which will cause the dbglevel parameter passed to s3fs-fuse to be empty string like "dbglevel=".
This causes the s3fs-fuse driver to error out generating a kubernetes error event like:
102s Warning FailedMount pod/sat-test-satellite-template-czpqh-grid-creation-step-1056368244 MountVolume.SetUp failed for volume "pvc-bc6f7c49-2f71-499e-9cce-19ddcee7942f" : mount command failed, status: Failure, reason: Error mounting volume: s3fs mount failed: s3fs: option dbglevel has unknown parameter().
This is because of a code bug in the s3fs-provisioner check at https://github.com/IBM/ibmcloud-object-storage-plugin/blob/master/provisioner/ibm-s3fs-provisioner.go#L757 only checking for != "", when it should also be checking for a nil value.
If one defines the ibm.io/debug-level only as a storage-class property and not in as an attribute in the PVC, the created PV will set the ibm.io/debug-level attribute to nil, which will cause the dbglevel parameter passed to s3fs-fuse to be empty string like "dbglevel=".
This causes the s3fs-fuse driver to error out generating a kubernetes error event like:
This is because of a code bug in the s3fs-provisioner check at https://github.com/IBM/ibmcloud-object-storage-plugin/blob/master/provisioner/ibm-s3fs-provisioner.go#L757 only checking for != "", when it should also be checking for a nil value.