Bug #22836: ceph-volume doesn't add OSD's auth to Monitors when creating new BlueStore OSD - ceph-volume - Ceph

Actions

Copy link

Bug #22836

closed

ceph-volume doesn't add OSD's auth to Monitors when creating new BlueStore OSD

Added by pei jia about 6 years ago. Updated about 6 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Andrew Schoen

Target version:

% Done:

Source:

Tags:

Backport:

luminous

Regression:

Severity:

2 - major

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

When add new BlueStore OSD with ceph-volume command, the new OSD daemon fails to start with log
_get_class not permitted to load kvs _get_class not permitted to load lua _get_class not permitted to load sdk ... log_to_monitors {default=true} init authentication failed: (1) Operation not permitted.
After checking the ceph-volume command log, it turns out that it doesn't contain "ceph auth add osd.{osd-num} osd 'allow *' mon 'allow rwx' -i /var/lib/ceph/osd/osd.id/keyring".
If we use "ceph auth add ..." manually, the new OSD daemon will start correctly.

Files

ceph-volume command log.txt (4.27 KB) ceph-volume command log.txt

pei jia, 01/31/2018 02:31 AM

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Alfredo Deza about 6 years ago

Status changed from New to Need More Info

We can't replicate this issue when deploying OSDs. Do you have some configuration that requires these permissions? Without them, in our tests, the OSD starts up without problems.

You are right that ceph-volume will not add an 'allow rwx' to the keyring.

Actions

Copy link

Updated by Andrew Schoen about 6 years ago

I believe this bug is because of the use of --osd-id. This PR fixes the issue where auth is not created for an OSD if --osd-id is used: https://github.com/ceph/ceph/pull/20203

Actions

Copy link