Project

General

Profile

Actions

Bug #51821

closed

client is using insecure global_id reclaim

Added by Daniel Persson almost 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
documentation
Target version:
-
% Done:

0%

Source:
Community (user)
Tags:
Backport:
Regression:
No
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Hi everyone.

We are running an Octopus cluster at work with more than 30 clients, and I'm currently reviewing pacific if we want to upgrade in the future at work. I have a small cluster with 4 hosts at home with one OSD, MON, MGR, MDS each. All hosts are running Debian with the latest Ceph packages 16.2.4

I have two clients I'm reviewing. One client is a Ubuntu client 16.2.5 built from the source as there are no Raspberry PI 3 packages.

The other client is a Windows 10 running ceph-dokan. I get these warnings in the monitor console:

AUTH_INSECURE_GLOBAL_ID_RECLAIM: client is using insecure global_id reclaim
AUTH_INSECURE_GLOBAL_ID_RECLAIM_ALLOWED: mons are allowing insecure global_id reclaim

If I switch the configuration, so I don't allow insecure global id reclaim on the monitors, the clients can't connect. So how do I configure ceph-dokan and a Linux environment mounting a resource using the kernel module?

I guess there is a configuration option I need to add to the ceph.conf file, but I can't find any documentation around this topic.

Thank you for your response.

Best regards
Daniel

Actions

Also available in: Atom PDF