Description of problem: RGW Multi-site configuration remove a zone from a zonegroup and period update --commit gives error read_lastest_epoch # radosgw-admin period update --commit 2017-08-18 03:27:22.969035 7f73f051e9c0 1 error read_lastest_epoch .rgw.root:periods.a5bc1fc7-2206-4b73-a7c1-b1d0e6254757:staging.latest_epoch 2017-08-18 03:27:22.978337 7f73f051e9c0 1 error read_lastest_epoch .rgw.root:periods.856d97c0-d75b-4f39-ade0-0870a7451bcb.latest_epoch https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/2/html-single/object_gateway_guide_for_red_hat_enterprise_linux/#multi_site 5.5.4. Delete Default Zone Group and Zone # radosgw-admin zonegroup remove --rgw-zonegroup=default --rgw-zone=default # radosgw-admin period update --commit Version-Release number of selected component (if applicable): Red Hat Ceph Storage 2.3 How reproducible: Always
Looks like this error message is not causing any issue because RGW multi-site configuration works well and looks like it is information message of reading an epoch and not an error message. This is only happening when we are removing default zone from default zonegroup. I got this upstream ticket: http://tracker.ceph.com/issues/15319#note-6 and note-6 from Casey confirm my understanding. "That doesn't appear to be an actual failure, just an intermediate check that we should probably be hiding from the user."
Okay so I got this commit and it moved from 0 to 1, I think better it should have been sent to 20 :) git show 55460e2e7b0f1298796b37b38a64820a8f23f6e2 commit 55460e2e7b0f1298796b37b38a64820a8f23f6e2 Author: Shilpa Jagannath <smanjara> Date: Sat Aug 6 14:25:48 2016 +0530 rgw: raise log levels for common radosgw-admin errors Currently while running radosgw-admin command we see these messages thrown at the endusers since debug level is set to 0: 2016-08-02 14:48:28.687251 7f9e630639c0 0 Cannot find zone id=7a2a89b9-4f5e-4f60-a29e-451ac9acc5a8 (name=us-west), switching to local zonegroup configuration 2016-08-02 14:48:35.742185 7f9e630639c0 0 error read_lastest_epoch .rgw.root:periods.a3db7884-2445-4bab-a165-6730f8573b8f:staging.latest_epoch Raising the log level to 1. Fixes: http://tracker.ceph.com/issues/16935 Signed-off-by: Shilpa Jagannath <smanjara> (cherry picked from commit 8ff2b8e71abd34648c8eefb6b158ae5de46bd709) $ git tag --contains 55460e2e7b0f1298796b37b38a64820a8f23f6e2 v10.2.3 v10.2.4 v10.2.5 v10.2.6 v10.2.7 v10.2.8 v10.2.9 $ git tag --contains 8ff2b8e71abd34648c8eefb6b158ae5de46bd709 v11.0.1 v11.0.2 v11.1.0 v11.1.1 v11.2.0 v11.2.1 v12.0.0 v12.0.1 v12.0.2 v12.0.3 v12.1.0 v12.1.1 v12.1.2 v12.1.3 v12.1.4 Casey, please let me know if sending a PR for log level 20 sounds good to you? I will send one.
Closed Next Release more details are given in upstream tracker - http://tracker.ceph.com/issues/21163