Project

General

Profile

Actions

Bug #14787

closed

Bug using bootstrap deployment mechasim with radosgw

Added by Rainer Goldmann about 8 years ago. Updated about 4 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

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

Description

hi,
we are using ceph on Debian jessy and are running into issues when using the bootstrap mechanism.

When we generate the keys with the command.

ceph --cluster ceph --name client.bootstrap-rgw --keyring /var/lib/ceph/bootstrap-rgw/ceph.keyring auth get-or-create client.rgw.<hostname> osd 'allow rwx' mon 'allow rw' -o /var/lib/ceph/radosgw/ceph-rgw.<hostname>/keyring

This works fine. It seems the naming for the client MUST be client.rgw.<hostname>.
Problem is the radowgw init script looks through the ceph.conf and only matches on
PREFIX='client.radosgw.'

(see https://github.com/ceph/ceph/blob/019a93f6bc98c094fa0338272d75947e7e6715f1/src/init-radosgw line 45)

This is not found because its called client.rgw.<hostname>.
The tool for creating the bootstap keys seems to need to match the rgw name to client.rgw.<hostname>
What we do at the moment is patching the init script to:

-PREFIX='client.radosgw.'
+PREFIX='client.rgw.'

Would be great if you look into this!

Cheers Rainer

Actions #1

Updated by Casey Bodley about 4 years ago

  • Status changed from New to Won't Fix
Actions

Also available in: Atom PDF