Project

General

Profile

Actions

Bug #14819

open

RadosGW and OpenStack Kilo Keystone's integration fails

Added by Yogesh Deshmukh about 8 years ago. Updated about 8 years ago.

Status:
New
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

RadosGW is working fine with swift cli client. When tries to integrate with Keystone(1.2.0 version), rgw fails with an error message:

2016-02-19 17:13:09.131661 7f63294f7700 0 curl_easy_performed returned error: gnutls_handshake() failed: An unexpected TLS packet was received.
2016-02-19 17:13:09.131729 7f63294f7700 0 ERROR: keystone revocation processing returned error r=-22

Keystone access log:
192.168.10.96 - - [19/Feb/2016:17:13:09 +0530] "\x16\x03" 400 0 "-" "-"

keystone error log:
2016-02-19 17:13:09.082412 AH00566: request failed: invalid characters in URI

Attached ceph.conf file.

Any help would be appreciated.


Files

ceph.conf (1003 Bytes) ceph.conf Yogesh Deshmukh, 02/19/2016 11:50 AM
Actions #1

Updated by Yogesh Deshmukh about 8 years ago

Actions #2

Updated by Abhishek Lekshmanan about 8 years ago

Can you trust the keystone ssl cert (used at 35357 port) explicitly and see if the error still exists?

Actions #3

Updated by Yogesh Deshmukh about 8 years ago

I tried by coping ca.cert and signing_cert.pem on radosgw node and running following commands, but still it's showing same error.

openssl x509 -in /tmp/ca.pem -pubkey | sudo certutil -d /var/ceph/nss -A -n ca -t "TCu,Cu,Tuw"
openssl x509 -in /tmp/signing_cert.pem -pubkey | sudo certutil -A -d /var/ceph/nss -n signing_cert -t "P,P,P"

Actions #4

Updated by Yogesh Deshmukh about 8 years ago

Is that '-' in Keystone access log requests intended?

Actions

Also available in: Atom PDF