Bug #44644
cephadm: RGW: updating the spec doesn't update the mon store
Status:
New
Priority:
Normal
Assignee:
-
Category:
cephadm/rgw
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
when creating RGW running
# ceph orch apply rgw --realm_name=default --zone_name=default 1 monitor2:192.168.122.151 ["Deployed rgw.default.default.pnxfft on host 'monitor2'"]
RGW service is created and running on target host. Also ceph config is
updated:
mgr advanced mgr/orchestrator/orchestrator cephadm client.rgw.default advanced rgw_realm default client.rgw.default.default advanced rgw_zone default *
after updating RGW (going to change zone) ceph config contains
configurations for both - RGW with old zone name and new zone name.
On target host there is new service for rgw with new zone name along with
running RGW service with old zone name
mgr advanced mgr/orchestrator_cli/orchestrator cephadm client.rgw.default advanced rgw_realm default client.rgw.default.default advanced rgw_zone default client.rgw.realm1 advanced rgw_realm realm1 client.rgw.realm1.default advanced rgw_zone default
I suppose that update should perform changing of the name and not adding new
seervice. If user would like to add new service he would use 'add' parameter
instead of 'update'.
Related issues
History
#1 Updated by Sebastian Wagner about 1 year ago
- Related to Bug #44604: cephadm: RGW: missing spec / mon store validation added
#2 Updated by Sebastian Wagner about 1 year ago
- Related to Bug #44699: cephadm: removing services leaves configs behind added
#3 Updated by Sebastian Wagner 10 months ago
- Category changed from cephadm to cephadm/rgw
#4 Updated by Sebastian Wagner 8 months ago
Deleting realms, zones and RGW users is something we need to carefully think about. Under all circumstances we have to avoid automatic data deletion.
We're not there yet and this will take time.