Project

General

Profile

Documentation #10305

Update documentation on http://ceph.com/docs/master/radosgw/keystone/

Added by Vivek Cherian over 9 years ago. Updated about 4 years ago.

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

0%

Tags:
Backport:
Reviewed:
Affected Versions:
Pull request ID:

Description

Hi,

In the URL http://ceph.com/docs/master/radosgw/keystone/, where it mentions about converting the OpenSSL certificates that Keystone uses for creating the requests to the nss db format, the document is vague in the sense that it does not mention were to create the /var/ceph/nss directory. It should be explicitly stated that the directory should be created on the ceph radosgw node(s) and not on the Openstack node(s).

Due to the confusion created by the vagueness of the document, I created the directory /var/ceph/nss on the Openstack node instead of the ceph radosgw node.

My radgosgw did not get started due to this mistake, and I had to manually copy /var/ceph/nss from the openstack node to the ceph radosgw node to get it started.

I discussed with Loic on IRC and he suggested that I file ticket for this issue.

I am also attaching the strace for your kind perusal.

Kindly do the needful.

Thanks,
---
Vivek Varghese Cherian

radosgw-strace.txt View (72.9 KB) Vivek Cherian, 12/11/2014 11:33 PM

History

#1 Updated by Loïc Dachary over 9 years ago

  • Assignee deleted (Loïc Dachary)

Unassigning myself because I'm not the best candidate ;-)

#2 Updated by Mark Kirkwood over 9 years ago

In addition, this issue was pretty cryptic to debug (...a pun... I know) and it would have been pretty straightforward if we had seen an error message to the effect "invalid/missing certicicates in /var/ceph/nss", as opposed to a core dump.

#3 Updated by Zac Dover about 4 years ago

  • Status changed from New to Closed

This bug has been judged too old to fix. This is because either it is either 1) raised against a version of Ceph prior to Luminous, or 2) just really old, and untouched for so long that it is unlikely nowadays to represent a live documentation concern.

If you think that the closing of this bug is an error, raise another bug of a similar kind. If you think that the matter requires urgent attention, please let Zac Dover know at .

Also available in: Atom PDF