Yes it is required to stop the gateway while preforming the workaround. Your zone info changes will be stay I recommend using 10.2.3 (the same version) for all gateways. On Wed, Nov 2, 2016 at 1:28 PM, Mustafa Muhammad <mustafa1024m@xxxxxxxxx> wrote: > Thanks a lot, I'll apply it when possible, but I've changed zone info > while RGWs are running before, is it strictly required to stop them? > They are all Jewel 10.2.2 > > Regards > Mustafa > > On Wed, Nov 2, 2016 at 12:39 PM, Orit Wasserman <owasserm@xxxxxxxxxx> wrote: >> Hi, >> You have hit the master zone issue. >> Here is a fix I prefer: >> http://lists.ceph.com/pipermail/ceph-users-ceph.com/2016-July/011157.html >> It is very important notice to run the fix when the radosgw is down. >> >> Good luck, >> Orit >> >> On Tue, Nov 1, 2016 at 10:07 PM, Mustafa Muhammad >> <mustafa1024m@xxxxxxxxx> wrote: >>> On Tue, Nov 1, 2016 at 5:04 PM, Orit Wasserman <owasserm@xxxxxxxxxx> wrote: >>>> Hi, >>>> what version of jewel are you using? >>>> can you try raodsgw-admin zone get --rgw-zone default and >>>> radosgw-admin zonegroup get --rgw-zonegroup default? >>>> >>> Hello, I am using 10.2.3 >>> #radosgw-admin zone get --rgw-zone default >>> { >>> "id": "default", >>> "name": "default", >>> "domain_root": ".rgw", >>> "control_pool": ".rgw.control", >>> "gc_pool": ".rgw.gc", >>> "log_pool": ".log", >>> "intent_log_pool": ".intent-log", >>> "usage_log_pool": ".usage", >>> "user_keys_pool": ".users", >>> "user_email_pool": ".users.email", >>> "user_swift_pool": ".users.swift", >>> "user_uid_pool": ".users.uid", >>> "system_key": { >>> "access_key": "", >>> "secret_key": "" >>> }, >>> "placement_pools": [], >>> "metadata_heap": ".rgw.meta", >>> "realm_id": "" >>> } >>> >>> # radosgw-admin zonegroup get --rgw-zonegroup default >>> { >>> "id": "default", >>> "name": "default", >>> "api_name": "", >>> "is_master": "true", >>> "endpoints": [], >>> "hostnames": [], >>> "hostnames_s3website": [], >>> "master_zone": "", >>> "zones": [ >>> { >>> "id": "default", >>> "name": "default", >>> "endpoints": [], >>> "log_meta": "false", >>> "log_data": "false", >>> "bucket_index_max_shards": 0, >>> "read_only": "false" >>> } >>> ], >>> "placement_targets": [ >>> { >>> "name": "cinema-placement", >>> "tags": [] >>> }, >>> { >>> "name": "cinema-source-placement", >>> "tags": [] >>> }, >>> { >>> "name": "default-placement", >>> "tags": [] >>> }, >>> { >>> "name": "erasure-placement", >>> "tags": [] >>> }, >>> { >>> "name": "share-placement", >>> "tags": [] >>> }, >>> { >>> "name": "share2016-placement", >>> "tags": [] >>> }, >>> { >>> "name": "test-placement", >>> "tags": [] >>> } >>> ], >>> "default_placement": "default-placement", >>> "realm_id": "" >>> } >>> >>> >>> Thanks >>> Mustafa >>> >>>> Orit >>>> >>>> On Tue, Nov 1, 2016 at 2:13 PM, Mustafa Muhammad <mustafa1024m@xxxxxxxxx> wrote: >>>>> Hello, >>>>> I have production cluster configured with multiple placement pools according to: >>>>> >>>>> http://cephnotes.ksperis.com/blog/2014/11/28/placement-pools-on-rados-gw >>>>> >>>>> After upgrading to Jewel, most radosgw-admin are failing, probably >>>>> because there is no realm >>>>> >>>>> >>>>> # radosgw-admin realm list >>>>> { >>>>> "default_info": "", >>>>> "realms": [] >>>>> } >>>>> >>>>> >>>>> # radosgw-admin zone get >>>>> unable to initialize zone: (2) No such file or directory >>>>> >>>>> >>>>> # radosgw-admin regionmap get >>>>> failed to read current period info: 2016-11-01 16:08:14.099948 >>>>> 7f21b55ee9c0 0 RGWPeriod::init failed to init realm id : (2) No >>>>> such file or directory(2) No such file or directory >>>>> { >>>>> "zonegroups": [], >>>>> "master_zonegroup": "", >>>>> "bucket_quota": { >>>>> "enabled": false, >>>>> "max_size_kb": -1, >>>>> "max_objects": -1 >>>>> }, >>>>> "user_quota": { >>>>> "enabled": false, >>>>> "max_size_kb": -1, >>>>> "max_objects": -1 >>>>> } >>>>> } >>>>> >>>>> >>>>> # radosgw-admin bucket stats >>>>> 2016-11-01 16:07:55.860053 7f6e747f89c0 0 zonegroup default missing >>>>> zone for master_zone= >>>>> couldn't init storage provider >>>>> >>>>> I have previous region.conf.json and zone.conf.json, how can I make >>>>> everything work again? Will creating new realm fix this? >>>>> >>>>> Regards >>>>> Mustafa Muhammad >>>>> -- >>>>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in >>>>> the body of a message to majordomo@xxxxxxxxxxxxxxx >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
