Project

General

Profile

Bug #22777

uniqueness of rgw service name not guaranteed

Added by Dan van der Ster about 6 years ago. Updated about 6 years ago.

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

0%

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

Description

Historically in our deployment we reuse the same client.radosgw key for all rgw's.
During the jewel/luminous upgrade we noticed that rgw infers a "service name" from that client name, then registers itself to the service map using the same name (rgw.radosgw in our case).
The obvious result is that no matter how many rgw's we have, the ceph service map only shows 1 single running rgw. e.g.:

> ceph versions
"rgw": {
"ceph version 12.2.2 (cf0baeeeeba3b47f9427c6c97e2144b094b7e5ba) luminous (stable)": 1
},

Are there other more serious operational problems which could result from this? If yes, we should probably teach rgw to refuse to start with a non-unique service name.

History

#1 Updated by Chang Liu about 6 years ago

I also noticed this problem while I impl the RGW page in mgr/dashboard. RGW daemons report their status via service name, so ceph-mgr plugins will not work as expected.

Also available in: Atom PDF