extblkdev/fcm: Do not enable set_keepcaps by default

When one runs FCM enabled hardware config.set_keepcaps must be set.
However, having it as default is inadvised.

Signed-off-by: Adam Kupczyk <akupczyk@ibm.com>
(cherry picked from commit dfb43c0d4e9fa4013b2a1e0367bee88a706497e5)

diff --git a/src/common/options/osd.yaml.in b/src/common/options/osd.yaml.in
index e56606aa37ef3800b779d7fc8397f0a551e23cc0..3ebf80022b5c0d2c517e474e7ecb2b011a0b74e6 100644 (file)
--- a/src/common/options/osd.yaml.in
+++ b/src/common/options/osd.yaml.in
@@ -34,7 +34,7 @@ options:
   long_desc: When ceph switches from root to the ceph uid, all capabilities in all sets are eraseed. If
     a component that is capability aware needs a specific capability, the keepcaps flag maintains
      the permitted capability set, allowing the capabilities in the effective set to be activated as needed.
-  default: true
+  default: false
   flags:
   - startup
 - name: osd_smart_report_timeout