Actions
Bug #43681
closedcephadm: Streamline RGW deployment
Status:
Resolved
Priority:
Normal
Assignee:
Daniel Pivonka
Category:
cephadm/rgw
Target version:
% Done:
0%
Source:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Tags (freeform):
Merge Commit:
Fixed In:
v16.0.0-3956-g0f7c912288
Released In:
v16.2.0~1827
Upkeep Timestamp:
2025-07-15T01:25:19+00:00
Description
The problem is, this doesn't work:
service_type: rgw
spec:
realm: myrealm
zone: myzone
and then:
cephadm bootstrap ... --apply-spec rgw.yaml
because
- Users need to run some commands manually:
radosgw-admin realm create --rgw-realm=default --default radosgw-admin zonegroup create --rgw-zonegroup=default --master --default radosgw-admin zone create --rgw-zonegroup=default --rgw-zone=default --master --
- Calling
realm createrequires running OSDs.
Which means, we have to:
- wait, till we have OSDs in the cluster
- Then, run those radosgw-admin commands.
Updated by Sebastian Wagner over 5 years ago
- Tracker changed from Feature to Bug
- Subject changed from multsite rgw to cephadm: Streamline RGW deployment
- Description updated (diff)
- Target version deleted (
v15.0.0) - Regression set to No
- Severity set to 3 - minor
Updated by Sebastian Wagner over 5 years ago
- Priority changed from Normal to High
Updated by Sebastian Wagner over 5 years ago
- Priority changed from High to Normal
Updated by Sebastian Wagner over 5 years ago
- Category changed from cephadm to cephadm/rgw
Updated by Sebastian Wagner over 5 years ago
- Assignee changed from Adam King to Daniel Pivonka
Updated by Sebastian Wagner over 5 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 36162
Updated by Sebastian Wagner over 5 years ago
- Has duplicate Bug #46385: Can i run rados and s3 compatible object storage device in Cephadm? added
Updated by Sebastian Wagner over 5 years ago
- Status changed from Fix Under Review to Resolved
- Target version set to v15.2.5
Updated by Upkeep Bot 8 months ago
- Merge Commit set to 0f7c912288e87760b3cad3e1ada88d7241284ec4
- Fixed In set to v16.0.0-3956-g0f7c912288
- Released In set to v16.2.0~1827
- Upkeep Timestamp set to 2025-07-15T01:25:19+00:00
Actions