Bug #6134: RGW returns an error on set_worker_bound if a zone's log_pool doesn't already exist - rgw - Ceph

Actions

Copy link

Bug #6134

closed

RGW returns an error on set_worker_bound if a zone's log_pool doesn't already exist

Added by Anonymous over 10 years ago. Updated over 10 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Yehuda Sadeh

Target version:

% Done:

Source:

other

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

At present, when a zone is configured, if its 'log_pool" doesn't happen to already exist, then RGW runs into issues. Specifically, the REST call set_worker_bound returns a 404 and logs this:

7f136cff9700 2 req 5:0.000366::POST /admin/replica_log:replicamdlog_updatebounds:verifying op params
7f136cff9700 2 req 5:0.000369::POST /admin/replica_log:replicamdlog_updatebounds:executing
7f136cff9700 -1 ERROR: could not open rados pool .region1.r1z1.log_pool
7f136cff9700 2 req 5:0.000436::POST /admin/replica_log:replicamdlog_updatebounds:http status=404

We should come up with something a bit more clean. Maybe we should create the pool on region-map update if it doesn't exist already? Or just document it in the setup guide?