Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Orit, your instructions to the workaround has helped to solve the bucket creation problems that I had. again, many thanks for your help Andrei - Original Message - > From: "Orit Wasserman" <owass...@redhat.com> > To: "Andrei Mikhailovsky" <and...@arhont.com> > Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" > <ceph-users@lists.ceph.com> > Sent: Saturday, 12 November, 2016 13:22:02 > Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket > On Fri, Nov 11, 2016 at 11:27 PM, Andrei Mikhailovsky <and...@arhont.com> > wrote: >> Hi Orit, >> >> Many thanks. I will try that over the weekend and let you know. >> >> Are you sure removing the pool will not destroy my data, user info and >> buckets? >> > > No this pool (.rgw.root) contains only the configuration (realm, > zonegroups and zones). > If you want to back it up run: > # rados mkpool .rgw.root.backup > # rados cppool .rgw.root .rgw.root.backup > > Orit >> Thanks >> >> - Original Message - >>> From: "Orit Wasserman" <owass...@redhat.com> >>> To: "andrei" <and...@arhont.com> >>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>> <ceph-users@lists.ceph.com> >>> Sent: Friday, 11 November, 2016 11:24:51 >>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket >> >>> I have a workaround: >>> >>> 1. Use zonegroup and zone jsons you have from before (default-zg.json >>> and default-zone.json) >>> 2. Make sure the realm id in the jsons is "" >>> 3. Stop the gateways >>> 4. Remove .rgw.root pool(you can back it up if you want to by using >>> mkpool and cppool commands): >>>rados rm .rgw.root >>> 5. radosgw-admin realm create --rgw-realm=myrealm >>> 6. radosgw-admin zonegroup set --rgw-zonegroup=default --default < >>> default-zg.json >>> 7. radosgw-admin zone set --rgw-zone=default --deault < default-zone.json >>> 8. radosgw-admin period update --commit >>> >>> Good luck, >>> Orit >>> >>> On Thu, Nov 10, 2016 at 7:08 PM, Andrei Mikhailovsky <and...@arhont.com> >>> wrote: >>>> >>>> Orit, here is the output: >>>> >>>> root@arh-ibstorage2-ib:~# rados ls -p .rgw.root >>>> region_map >>>> default.zone.5b41b1b2-0f92-463d-b582-07552f83e66c >>>> realms.5b41b1b2-0f92-463d-b582-07552f83e66c >>>> zonegroups_names.default >>>> zone_names.default >>>> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.1 >>>> realms_names.default >>>> realms_names.london-ldex >>>> realms.f08592f2-5d53-4701-a895-b780b16b5374 >>>> periods.286475fa-625b-4fdb-97bf-dcec4b437960.latest_epoch >>>> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging >>>> periods.286475fa-625b-4fdb-97bf-dcec4b437960.1 >>>> default.realm >>>> default.zonegroup.5b41b1b2-0f92-463d-b582-07552f83e66c >>>> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.latest_epoch >>>> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging.latest_epoch >>>> realms.f08592f2-5d53-4701-a895-b780b16b5374.control >>>> zone_info.default >>>> zonegroup_info.default >>>> realms.5b41b1b2-0f92-463d-b582-07552f83e66c.control >>>> >>>> >>>> Thanks >>>> >>>> - Original Message - >>>>> From: "Orit Wasserman" <owass...@redhat.com> >>>>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>>>> <ceph-users@lists.ceph.com> >>>>> Sent: Thursday, 10 November, 2016 15:22:16 >>>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a >>>>> bucket >>>> >>>>> On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com> >>>>> wrote: >>>>>> Orit, true. >>>>>> >>>>>> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I >>>>>> have a >>>>>> small cluster and I always update all servers at once. >>>>>> >>>>>> I don't have any Hammer releases of ceph anywhere on the network. >>>>>> >
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Thanks! I am doing this now. Will update if this works. Thanks for your help everyone! - Original Message - > From: "Orit Wasserman" <owass...@redhat.com> > To: "andrei" <and...@arhont.com> > Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" > <ceph-users@lists.ceph.com> > Sent: Saturday, 12 November, 2016 13:22:02 > Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket > On Fri, Nov 11, 2016 at 11:27 PM, Andrei Mikhailovsky <and...@arhont.com> > wrote: >> Hi Orit, >> >> Many thanks. I will try that over the weekend and let you know. >> >> Are you sure removing the pool will not destroy my data, user info and >> buckets? >> > > No this pool (.rgw.root) contains only the configuration (realm, > zonegroups and zones). > If you want to back it up run: > # rados mkpool .rgw.root.backup > # rados cppool .rgw.root .rgw.root.backup > > Orit >> Thanks >> >> - Original Message - >>> From: "Orit Wasserman" <owass...@redhat.com> >>> To: "andrei" <and...@arhont.com> >>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>> <ceph-users@lists.ceph.com> >>> Sent: Friday, 11 November, 2016 11:24:51 >>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket >> >>> I have a workaround: >>> >>> 1. Use zonegroup and zone jsons you have from before (default-zg.json >>> and default-zone.json) >>> 2. Make sure the realm id in the jsons is "" >>> 3. Stop the gateways >>> 4. Remove .rgw.root pool(you can back it up if you want to by using >>> mkpool and cppool commands): >>>rados rm .rgw.root >>> 5. radosgw-admin realm create --rgw-realm=myrealm >>> 6. radosgw-admin zonegroup set --rgw-zonegroup=default --default < >>> default-zg.json >>> 7. radosgw-admin zone set --rgw-zone=default --deault < default-zone.json >>> 8. radosgw-admin period update --commit >>> >>> Good luck, >>> Orit >>> >>> On Thu, Nov 10, 2016 at 7:08 PM, Andrei Mikhailovsky <and...@arhont.com> >>> wrote: >>>> >>>> Orit, here is the output: >>>> >>>> root@arh-ibstorage2-ib:~# rados ls -p .rgw.root >>>> region_map >>>> default.zone.5b41b1b2-0f92-463d-b582-07552f83e66c >>>> realms.5b41b1b2-0f92-463d-b582-07552f83e66c >>>> zonegroups_names.default >>>> zone_names.default >>>> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.1 >>>> realms_names.default >>>> realms_names.london-ldex >>>> realms.f08592f2-5d53-4701-a895-b780b16b5374 >>>> periods.286475fa-625b-4fdb-97bf-dcec4b437960.latest_epoch >>>> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging >>>> periods.286475fa-625b-4fdb-97bf-dcec4b437960.1 >>>> default.realm >>>> default.zonegroup.5b41b1b2-0f92-463d-b582-07552f83e66c >>>> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.latest_epoch >>>> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging.latest_epoch >>>> realms.f08592f2-5d53-4701-a895-b780b16b5374.control >>>> zone_info.default >>>> zonegroup_info.default >>>> realms.5b41b1b2-0f92-463d-b582-07552f83e66c.control >>>> >>>> >>>> Thanks >>>> >>>> - Original Message - >>>>> From: "Orit Wasserman" <owass...@redhat.com> >>>>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>>>> <ceph-users@lists.ceph.com> >>>>> Sent: Thursday, 10 November, 2016 15:22:16 >>>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a >>>>> bucket >>>> >>>>> On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com> >>>>> wrote: >>>>>> Orit, true. >>>>>> >>>>>> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I >>>>>> have a >>>>>> small cluster and I always update all servers at once. >>>>>> >>>>>> I don't have any Hammer releases of ceph anywhere on the network. >>>>>> >>>>> >>>>> can you run: rados ls .rgw.root? >
Re: [ceph-users] radosgw - http status 400 while creating a bucket
On Fri, Nov 11, 2016 at 11:27 PM, Andrei Mikhailovsky <and...@arhont.com> wrote: > Hi Orit, > > Many thanks. I will try that over the weekend and let you know. > > Are you sure removing the pool will not destroy my data, user info and > buckets? > No this pool (.rgw.root) contains only the configuration (realm, zonegroups and zones). If you want to back it up run: # rados mkpool .rgw.root.backup # rados cppool .rgw.root .rgw.root.backup Orit > Thanks > > - Original Message - >> From: "Orit Wasserman" <owass...@redhat.com> >> To: "andrei" <and...@arhont.com> >> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >> <ceph-users@lists.ceph.com> >> Sent: Friday, 11 November, 2016 11:24:51 >> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket > >> I have a workaround: >> >> 1. Use zonegroup and zone jsons you have from before (default-zg.json >> and default-zone.json) >> 2. Make sure the realm id in the jsons is "" >> 3. Stop the gateways >> 4. Remove .rgw.root pool(you can back it up if you want to by using >> mkpool and cppool commands): >>rados rm .rgw.root >> 5. radosgw-admin realm create --rgw-realm=myrealm >> 6. radosgw-admin zonegroup set --rgw-zonegroup=default --default < >> default-zg.json >> 7. radosgw-admin zone set --rgw-zone=default --deault < default-zone.json >> 8. radosgw-admin period update --commit >> >> Good luck, >> Orit >> >> On Thu, Nov 10, 2016 at 7:08 PM, Andrei Mikhailovsky <and...@arhont.com> >> wrote: >>> >>> Orit, here is the output: >>> >>> root@arh-ibstorage2-ib:~# rados ls -p .rgw.root >>> region_map >>> default.zone.5b41b1b2-0f92-463d-b582-07552f83e66c >>> realms.5b41b1b2-0f92-463d-b582-07552f83e66c >>> zonegroups_names.default >>> zone_names.default >>> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.1 >>> realms_names.default >>> realms_names.london-ldex >>> realms.f08592f2-5d53-4701-a895-b780b16b5374 >>> periods.286475fa-625b-4fdb-97bf-dcec4b437960.latest_epoch >>> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging >>> periods.286475fa-625b-4fdb-97bf-dcec4b437960.1 >>> default.realm >>> default.zonegroup.5b41b1b2-0f92-463d-b582-07552f83e66c >>> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.latest_epoch >>> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging.latest_epoch >>> realms.f08592f2-5d53-4701-a895-b780b16b5374.control >>> zone_info.default >>> zonegroup_info.default >>> realms.5b41b1b2-0f92-463d-b582-07552f83e66c.control >>> >>> >>> Thanks >>> >>> - Original Message - >>>> From: "Orit Wasserman" <owass...@redhat.com> >>>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>>> <ceph-users@lists.ceph.com> >>>> Sent: Thursday, 10 November, 2016 15:22:16 >>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket >>> >>>> On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com> >>>> wrote: >>>>> Orit, true. >>>>> >>>>> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I have >>>>> a >>>>> small cluster and I always update all servers at once. >>>>> >>>>> I don't have any Hammer releases of ceph anywhere on the network. >>>>> >>>> >>>> can you run: rados ls .rgw.root? >>>> >>>>> Is 10.2.4 out already? I didn't see an update package to that. >>>>> >>>> >>>> It should be out soon >>>> >>>>> Thanks >>>>> >>>>> Andrei >>>>> >>>>> - Original Message - >>>>>> From: "Orit Wasserman" <owass...@redhat.com> >>>>>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>>>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>>>>> <ceph-users@lists.ceph.com> >>>>>> Sent: Thursday, 10 November, 2016 13:58:32 >>>>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a >>>>>> bucket >>>>> >>>
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Orit, Many thanks. I will try that over the weekend and let you know. Are you sure removing the pool will not destroy my data, user info and buckets? Thanks - Original Message - > From: "Orit Wasserman" <owass...@redhat.com> > To: "andrei" <and...@arhont.com> > Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" > <ceph-users@lists.ceph.com> > Sent: Friday, 11 November, 2016 11:24:51 > Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket > I have a workaround: > > 1. Use zonegroup and zone jsons you have from before (default-zg.json > and default-zone.json) > 2. Make sure the realm id in the jsons is "" > 3. Stop the gateways > 4. Remove .rgw.root pool(you can back it up if you want to by using > mkpool and cppool commands): >rados rm .rgw.root > 5. radosgw-admin realm create --rgw-realm=myrealm > 6. radosgw-admin zonegroup set --rgw-zonegroup=default --default < > default-zg.json > 7. radosgw-admin zone set --rgw-zone=default --deault < default-zone.json > 8. radosgw-admin period update --commit > > Good luck, > Orit > > On Thu, Nov 10, 2016 at 7:08 PM, Andrei Mikhailovsky <and...@arhont.com> > wrote: >> >> Orit, here is the output: >> >> root@arh-ibstorage2-ib:~# rados ls -p .rgw.root >> region_map >> default.zone.5b41b1b2-0f92-463d-b582-07552f83e66c >> realms.5b41b1b2-0f92-463d-b582-07552f83e66c >> zonegroups_names.default >> zone_names.default >> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.1 >> realms_names.default >> realms_names.london-ldex >> realms.f08592f2-5d53-4701-a895-b780b16b5374 >> periods.286475fa-625b-4fdb-97bf-dcec4b437960.latest_epoch >> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging >> periods.286475fa-625b-4fdb-97bf-dcec4b437960.1 >> default.realm >> default.zonegroup.5b41b1b2-0f92-463d-b582-07552f83e66c >> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.latest_epoch >> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging.latest_epoch >> realms.f08592f2-5d53-4701-a895-b780b16b5374.control >> zone_info.default >> zonegroup_info.default >> realms.5b41b1b2-0f92-463d-b582-07552f83e66c.control >> >> >> Thanks >> >> ----- Original Message - >>> From: "Orit Wasserman" <owass...@redhat.com> >>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>> <ceph-users@lists.ceph.com> >>> Sent: Thursday, 10 November, 2016 15:22:16 >>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket >> >>> On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com> >>> wrote: >>>> Orit, true. >>>> >>>> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I have a >>>> small cluster and I always update all servers at once. >>>> >>>> I don't have any Hammer releases of ceph anywhere on the network. >>>> >>> >>> can you run: rados ls .rgw.root? >>> >>>> Is 10.2.4 out already? I didn't see an update package to that. >>>> >>> >>> It should be out soon >>> >>>> Thanks >>>> >>>> Andrei >>>> >>>> - Original Message - >>>>> From: "Orit Wasserman" <owass...@redhat.com> >>>>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>>>> <ceph-users@lists.ceph.com> >>>>> Sent: Thursday, 10 November, 2016 13:58:32 >>>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a >>>>> bucket >>>> >>>>> On Thu, Nov 10, 2016 at 2:55 PM, Andrei Mikhailovsky <and...@arhont.com> >>>>> wrote: >>>>>> Orit, >>>>>> >>>>>> Here is what i've done just now: >>>>>> >>>>>> root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway stop >>>>>> >>>>>> (the above command was ran on both radosgw servers). Checked with ps and >>>>>> no >>>>>> radosgw services were running. After that I've done: >>>>>> >>>>>> >>>>>> >>>>>> root@arh-ibstorage1-ib:~# ./ceph-zones-fix.sh
Re: [ceph-users] radosgw - http status 400 while creating a bucket
On Fri, Nov 11, 2016 at 12:24 PM, Orit Wasserman <owass...@redhat.com> wrote: > I have a workaround: > > 1. Use zonegroup and zone jsons you have from before (default-zg.json > and default-zone.json) > 2. Make sure the realm id in the jsons is "" > 3. Stop the gateways > 4. Remove .rgw.root pool(you can back it up if you want to by using > mkpool and cppool commands): > rados rm .rgw.root it should be: rados rmpool .rgw.root > 5. radosgw-admin realm create --rgw-realm=myrealm > 6. radosgw-admin zonegroup set --rgw-zonegroup=default --default < > default-zg.json > 7. radosgw-admin zone set --rgw-zone=default --deault < default-zone.json > 8. radosgw-admin period update --commit > > Good luck, > Orit > > On Thu, Nov 10, 2016 at 7:08 PM, Andrei Mikhailovsky <and...@arhont.com> > wrote: >> >> Orit, here is the output: >> >> root@arh-ibstorage2-ib:~# rados ls -p .rgw.root >> region_map >> default.zone.5b41b1b2-0f92-463d-b582-07552f83e66c >> realms.5b41b1b2-0f92-463d-b582-07552f83e66c >> zonegroups_names.default >> zone_names.default >> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.1 >> realms_names.default >> realms_names.london-ldex >> realms.f08592f2-5d53-4701-a895-b780b16b5374 >> periods.286475fa-625b-4fdb-97bf-dcec4b437960.latest_epoch >> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging >> periods.286475fa-625b-4fdb-97bf-dcec4b437960.1 >> default.realm >> default.zonegroup.5b41b1b2-0f92-463d-b582-07552f83e66c >> periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.latest_epoch >> periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging.latest_epoch >> realms.f08592f2-5d53-4701-a895-b780b16b5374.control >> zone_info.default >> zonegroup_info.default >> realms.5b41b1b2-0f92-463d-b582-07552f83e66c.control >> >> >> Thanks >> >> - Original Message - >>> From: "Orit Wasserman" <owass...@redhat.com> >>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>> <ceph-users@lists.ceph.com> >>> Sent: Thursday, 10 November, 2016 15:22:16 >>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket >> >>> On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com> >>> wrote: >>>> Orit, true. >>>> >>>> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I have a >>>> small cluster and I always update all servers at once. >>>> >>>> I don't have any Hammer releases of ceph anywhere on the network. >>>> >>> >>> can you run: rados ls .rgw.root? >>> >>>> Is 10.2.4 out already? I didn't see an update package to that. >>>> >>> >>> It should be out soon >>> >>>> Thanks >>>> >>>> Andrei >>>> >>>> - Original Message - >>>>> From: "Orit Wasserman" <owass...@redhat.com> >>>>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>>>> <ceph-users@lists.ceph.com> >>>>> Sent: Thursday, 10 November, 2016 13:58:32 >>>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a >>>>> bucket >>>> >>>>> On Thu, Nov 10, 2016 at 2:55 PM, Andrei Mikhailovsky <and...@arhont.com> >>>>> wrote: >>>>>> Orit, >>>>>> >>>>>> Here is what i've done just now: >>>>>> >>>>>> root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway stop >>>>>> >>>>>> (the above command was ran on both radosgw servers). Checked with ps and >>>>>> no >>>>>> radosgw services were running. After that I've done: >>>>>> >>>>>> >>>>>> >>>>>> root@arh-ibstorage1-ib:~# ./ceph-zones-fix.sh >>>>>> + RADOSGW_ADMIN=radosgw-admin >>>>>> + echo Exercise initialization code >>>>>> Exercise initialization code >>>>>> + radosgw-admin user info --uid=foo >>>>>> could not fetch user info: no user info saved >>>>>> + echo Get default zonegroup >>>>>> Get default zonegroup >>>>>> + rad
Re: [ceph-users] radosgw - http status 400 while creating a bucket
I have a workaround: 1. Use zonegroup and zone jsons you have from before (default-zg.json and default-zone.json) 2. Make sure the realm id in the jsons is "" 3. Stop the gateways 4. Remove .rgw.root pool(you can back it up if you want to by using mkpool and cppool commands): rados rm .rgw.root 5. radosgw-admin realm create --rgw-realm=myrealm 6. radosgw-admin zonegroup set --rgw-zonegroup=default --default < default-zg.json 7. radosgw-admin zone set --rgw-zone=default --deault < default-zone.json 8. radosgw-admin period update --commit Good luck, Orit On Thu, Nov 10, 2016 at 7:08 PM, Andrei Mikhailovsky <and...@arhont.com> wrote: > > Orit, here is the output: > > root@arh-ibstorage2-ib:~# rados ls -p .rgw.root > region_map > default.zone.5b41b1b2-0f92-463d-b582-07552f83e66c > realms.5b41b1b2-0f92-463d-b582-07552f83e66c > zonegroups_names.default > zone_names.default > periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.1 > realms_names.default > realms_names.london-ldex > realms.f08592f2-5d53-4701-a895-b780b16b5374 > periods.286475fa-625b-4fdb-97bf-dcec4b437960.latest_epoch > periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging > periods.286475fa-625b-4fdb-97bf-dcec4b437960.1 > default.realm > default.zonegroup.5b41b1b2-0f92-463d-b582-07552f83e66c > periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.latest_epoch > periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging.latest_epoch > realms.f08592f2-5d53-4701-a895-b780b16b5374.control > zone_info.default > zonegroup_info.default > realms.5b41b1b2-0f92-463d-b582-07552f83e66c.control > > > Thanks > > - Original Message - >> From: "Orit Wasserman" <owass...@redhat.com> >> To: "Andrei Mikhailovsky" <and...@arhont.com> >> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >> <ceph-users@lists.ceph.com> >> Sent: Thursday, 10 November, 2016 15:22:16 >> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket > >> On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com> >> wrote: >>> Orit, true. >>> >>> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I have a >>> small cluster and I always update all servers at once. >>> >>> I don't have any Hammer releases of ceph anywhere on the network. >>> >> >> can you run: rados ls .rgw.root? >> >>> Is 10.2.4 out already? I didn't see an update package to that. >>> >> >> It should be out soon >> >>> Thanks >>> >>> Andrei >>> >>> - Original Message - >>>> From: "Orit Wasserman" <owass...@redhat.com> >>>> To: "Andrei Mikhailovsky" <and...@arhont.com> >>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users" >>>> <ceph-users@lists.ceph.com> >>>> Sent: Thursday, 10 November, 2016 13:58:32 >>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket >>> >>>> On Thu, Nov 10, 2016 at 2:55 PM, Andrei Mikhailovsky <and...@arhont.com> >>>> wrote: >>>>> Orit, >>>>> >>>>> Here is what i've done just now: >>>>> >>>>> root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway stop >>>>> >>>>> (the above command was ran on both radosgw servers). Checked with ps and >>>>> no >>>>> radosgw services were running. After that I've done: >>>>> >>>>> >>>>> >>>>> root@arh-ibstorage1-ib:~# ./ceph-zones-fix.sh >>>>> + RADOSGW_ADMIN=radosgw-admin >>>>> + echo Exercise initialization code >>>>> Exercise initialization code >>>>> + radosgw-admin user info --uid=foo >>>>> could not fetch user info: no user info saved >>>>> + echo Get default zonegroup >>>>> Get default zonegroup >>>>> + radosgw-admin zonegroup get --rgw-zonegroup=default >>>>> + sed s/"id":.*/"id": "default",/g >>>>> + sed s/"master_zone.*/"master_zone": "default",/g >>>>> + echo Get default zone >>>>> Get default zone >>>>> + radosgw-admin zone get --zone-id=default >>>>> + echo Creating realm >>>>> Creating realm >>>>> + radosgw-admin realm create --rgw-realm=london-ldex >>>>> ERROR: couldn't create realm london-ldex: (17) F
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Daniel, how would I check what server is the master and how do I set it? cheers - Original Message - > From: "Daniel Gryniewicz" <d...@redhat.com> > To: "ceph-users" <ceph-users@lists.ceph.com> > Sent: Thursday, 10 November, 2016 15:08:55 > Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket > Your RGW doesn't think it's the master, and cannot connect to the > master, thus the create fails. > > Daniel > > On 11/08/2016 06:36 PM, Andrei Mikhailovsky wrote: >> Hello >> >> I am having issues with creating buckets in radosgw. It started with an >> upgrade to version 10.2.x >> >> When I am creating a bucket I get the following error on the client side: >> >> >> boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request >> > encoding="UTF-8"?>InvalidArgumentmy-new-bucket-31337tx2-0058225bae-994d148-default994d148-default-default >> >> >> The radosgw logs are (redacted): >> >> ### >> >> 2016-11-08 23:11:42.876862 7f026d953700 20 enqueued request >> req=0x7f02ba07b0e0 >> 2016-11-08 23:11:42.876892 7f026d953700 20 RGWWQ: >> 2016-11-08 23:11:42.876897 7f026d953700 20 req: 0x7f02ba07b0e0 >> 2016-11-08 23:11:42.876912 7f026d953700 10 allocated request >> req=0x7f02ba07b140 >> 2016-11-08 23:11:42.876975 7f026b94f700 20 dequeued request >> req=0x7f02ba07b0e0 >> 2016-11-08 23:11:42.876987 7f026b94f700 20 RGWWQ: empty >> 2016-11-08 23:11:42.877050 7f026b94f700 20 CONTENT_LENGTH=0 >> 2016-11-08 23:11:42.877060 7f026b94f700 20 CONTEXT_DOCUMENT_ROOT=/var/www >> 2016-11-08 23:11:42.877062 7f026b94f700 20 CONTEXT_PREFIX= >> 2016-11-08 23:11:42.877063 7f026b94f700 20 DOCUMENT_ROOT=/var/www >> 2016-11-08 23:11:42.877081 7f026b94f700 20 FCGI_ROLE=RESPONDER >> 2016-11-08 23:11:42.877083 7f026b94f700 20 GATEWAY_INTERFACE=CGI/1.1 >> 2016-11-08 23:11:42.877084 7f026b94f700 20 HTTP_ACCEPT_ENCODING=identity >> 2016-11-08 23:11:42.877086 7f026b94f700 20 HTTP_AUTHORIZATION=AWS >> XXXEDITEDXX:EDITEDXXXeWyiacaN26GcME >> 2016-11-08 23:11:42.877087 7f026b94f700 20 HTTP_DATE=Tue, 08 Nov 2016 >> 23:11:37 GMT >> 2016-11-08 23:11:42.877088 7f026b94f700 20 >> HTTP_HOST=s3service.editedname.com >> 2016-11-08 23:11:42.877089 7f026b94f700 20 HTTP_USER_AGENT=Boto/2.38.0 >> Python/2.7.12 Linux/4.8.4-040804-generic >> 2016-11-08 23:11:42.877090 7f026b94f700 20 HTTPS=on >> 2016-11-08 23:11:42.877092 7f026b94f700 20 >> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin >> 2016-11-08 23:11:42.877093 7f026b94f700 20 proxy-nokeepalive=1 >> 2016-11-08 23:11:42.877094 7f026b94f700 20 QUERY_STRING= >> 2016-11-08 23:11:42.877095 7f026b94f700 20 REMOTE_ADDR=192.168.169.91 >> 2016-11-08 23:11:42.877096 7f026b94f700 20 REMOTE_PORT=45404 >> 2016-11-08 23:11:42.877097 7f026b94f700 20 REQUEST_METHOD=PUT >> 2016-11-08 23:11:42.877098 7f026b94f700 20 REQUEST_SCHEME=https >> 2016-11-08 23:11:42.877099 7f026b94f700 20 REQUEST_URI=/my-new-bucket-31337/ >> 2016-11-08 23:11:42.877104 7f026b94f700 20 >> SCRIPT_FILENAME=proxy:fcgi://localhost:9000/my-new-bucket-31337/ >> 2016-11-08 23:11:42.877105 7f026b94f700 20 SCRIPT_NAME=/my-new-bucket-31337/ >> 2016-11-08 23:11:42.877107 7f026b94f700 20 >> SCRIPT_URI=https://s3service.editedname.com/my-new-bucket-31337/ >> 2016-11-08 23:11:42.877108 7f026b94f700 20 SCRIPT_URL=/my-new-bucket-31337/ >> 2016-11-08 23:11:42.877109 7f026b94f700 20 SERVER_ADDR=192.168.169.201 >> 2016-11-08 23:11:42.877110 7f026b94f700 20 >> SERVER_ADMIN=and...@editedname.com >> 2016-11-08 23:11:42.877111 7f026b94f700 20 >> SERVER_NAME=s3service.editedname.com >> 2016-11-08 23:11:42.877112 7f026b94f700 20 SERVER_PORT=443 >> 2016-11-08 23:11:42.877113 7f026b94f700 20 SERVER_PROTOCOL=HTTP/1.1 >> 2016-11-08 23:11:42.877114 7f026b94f700 20 SERVER_SIGNATURE= >> 2016-11-08 23:11:42.877115 7f026b94f700 20 SERVER_SOFTWARE=Apache/2.4.18 >> (Ubuntu) >> 2016-11-08 23:11:42.877116 7f026b94f700 20 >> SSL_TLS_SNI=s3service.editedname.com >> 2016-11-08 23:11:42.877119 7f026b94f700 1 == starting new request >> req=0x7f02ba07b0e0 = >> 2016-11-08 23:11:42.877155 7f026b94f700 2 req 2:0.35::PUT >> /my-new-bucket-31337/::initializing for trans_id = >> tx2-0058225bae-994d148-default >> 2016-11-08 23:11:42.877175 7f026b94f700 10 rgw api priority: s3=5 >> s3website=4 >> 2016-11-08 23:11:42.877179 7f026b94f700 10 host=s3service.editedname.com >> 2016-11-08 23:11:42.877199 7f026b94f700 20 subdom
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Orit, here is the output:
root@arh-ibstorage2-ib:~# rados ls -p .rgw.root
region_map
default.zone.5b41b1b2-0f92-463d-b582-07552f83e66c
realms.5b41b1b2-0f92-463d-b582-07552f83e66c
zonegroups_names.default
zone_names.default
periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.1
realms_names.default
realms_names.london-ldex
realms.f08592f2-5d53-4701-a895-b780b16b5374
periods.286475fa-625b-4fdb-97bf-dcec4b437960.latest_epoch
periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging
periods.286475fa-625b-4fdb-97bf-dcec4b437960.1
default.realm
default.zonegroup.5b41b1b2-0f92-463d-b582-07552f83e66c
periods.a9543371-a073-4d73-ab6d-0f54991c7ad9.latest_epoch
periods.5b41b1b2-0f92-463d-b582-07552f83e66c:staging.latest_epoch
realms.f08592f2-5d53-4701-a895-b780b16b5374.control
zone_info.default
zonegroup_info.default
realms.5b41b1b2-0f92-463d-b582-07552f83e66c.control
Thanks
- Original Message -
> From: "Orit Wasserman" <owass...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users"
> <ceph-users@lists.ceph.com>
> Sent: Thursday, 10 November, 2016 15:22:16
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com>
> wrote:
>> Orit, true.
>>
>> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I have a
>> small cluster and I always update all servers at once.
>>
>> I don't have any Hammer releases of ceph anywhere on the network.
>>
>
> can you run: rados ls .rgw.root?
>
>> Is 10.2.4 out already? I didn't see an update package to that.
>>
>
> It should be out soon
>
>> Thanks
>>
>> Andrei
>>
>> - Original Message -
>>> From: "Orit Wasserman" <owass...@redhat.com>
>>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users"
>>> <ceph-users@lists.ceph.com>
>>> Sent: Thursday, 10 November, 2016 13:58:32
>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>>
>>> On Thu, Nov 10, 2016 at 2:55 PM, Andrei Mikhailovsky <and...@arhont.com>
>>> wrote:
>>>> Orit,
>>>>
>>>> Here is what i've done just now:
>>>>
>>>> root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway stop
>>>>
>>>> (the above command was ran on both radosgw servers). Checked with ps and no
>>>> radosgw services were running. After that I've done:
>>>>
>>>>
>>>>
>>>> root@arh-ibstorage1-ib:~# ./ceph-zones-fix.sh
>>>> + RADOSGW_ADMIN=radosgw-admin
>>>> + echo Exercise initialization code
>>>> Exercise initialization code
>>>> + radosgw-admin user info --uid=foo
>>>> could not fetch user info: no user info saved
>>>> + echo Get default zonegroup
>>>> Get default zonegroup
>>>> + radosgw-admin zonegroup get --rgw-zonegroup=default
>>>> + sed s/"id":.*/"id": "default",/g
>>>> + sed s/"master_zone.*/"master_zone": "default",/g
>>>> + echo Get default zone
>>>> Get default zone
>>>> + radosgw-admin zone get --zone-id=default
>>>> + echo Creating realm
>>>> Creating realm
>>>> + radosgw-admin realm create --rgw-realm=london-ldex
>>>> ERROR: couldn't create realm london-ldex: (17) File exists
>>>> 2016-11-10 13:44:48.872839 7f87a13d9a00 0 ERROR creating new realm object
>>>> london-ldex: (17) File exists
>>>> + echo Creating default zonegroup
>>>> Creating default zonegroup
>>>> + radosgw-admin zonegroup set --rgw-zonegroup=default
>>>> {
>>>> "id": "default",
>>>> "name": "default",
>>>> "api_name": "",
>>>> "is_master": "true",
>>>> "endpoints": [],
>>>> "hostnames": [],
>>>> "hostnames_s3website": [],
>>>> "master_zone": "default",
>>>> "zones": [
>>>> {
>>>> "id": "default",
>>>> "name": "default",
>>>> "endpoints": [],
>>>> "log
Re: [ceph-users] radosgw - http status 400 while creating a bucket
On Thu, Nov 10, 2016 at 3:32 PM, Andrei Mikhailovsky <and...@arhont.com> wrote:
> Orit, true.
>
> yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I have a
> small cluster and I always update all servers at once.
>
> I don't have any Hammer releases of ceph anywhere on the network.
>
can you run: rados ls .rgw.root?
> Is 10.2.4 out already? I didn't see an update package to that.
>
It should be out soon
> Thanks
>
> Andrei
>
> - Original Message -
>> From: "Orit Wasserman" <owass...@redhat.com>
>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users"
>> <ceph-users@lists.ceph.com>
>> Sent: Thursday, 10 November, 2016 13:58:32
>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>
>> On Thu, Nov 10, 2016 at 2:55 PM, Andrei Mikhailovsky <and...@arhont.com>
>> wrote:
>>> Orit,
>>>
>>> Here is what i've done just now:
>>>
>>> root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway stop
>>>
>>> (the above command was ran on both radosgw servers). Checked with ps and no
>>> radosgw services were running. After that I've done:
>>>
>>>
>>>
>>> root@arh-ibstorage1-ib:~# ./ceph-zones-fix.sh
>>> + RADOSGW_ADMIN=radosgw-admin
>>> + echo Exercise initialization code
>>> Exercise initialization code
>>> + radosgw-admin user info --uid=foo
>>> could not fetch user info: no user info saved
>>> + echo Get default zonegroup
>>> Get default zonegroup
>>> + radosgw-admin zonegroup get --rgw-zonegroup=default
>>> + sed s/"id":.*/"id": "default",/g
>>> + sed s/"master_zone.*/"master_zone": "default",/g
>>> + echo Get default zone
>>> Get default zone
>>> + radosgw-admin zone get --zone-id=default
>>> + echo Creating realm
>>> Creating realm
>>> + radosgw-admin realm create --rgw-realm=london-ldex
>>> ERROR: couldn't create realm london-ldex: (17) File exists
>>> 2016-11-10 13:44:48.872839 7f87a13d9a00 0 ERROR creating new realm object
>>> london-ldex: (17) File exists
>>> + echo Creating default zonegroup
>>> Creating default zonegroup
>>> + radosgw-admin zonegroup set --rgw-zonegroup=default
>>> {
>>> "id": "default",
>>> "name": "default",
>>> "api_name": "",
>>> "is_master": "true",
>>> "endpoints": [],
>>> "hostnames": [],
>>> "hostnames_s3website": [],
>>> "master_zone": "default",
>>> "zones": [
>>> {
>>> "id": "default",
>>> "name": "default",
>>> "endpoints": [],
>>> "log_meta": "false",
>>> "log_data": "false",
>>> "bucket_index_max_shards": 0,
>>> "read_only": "false"
>>> }
>>> ],
>>> "placement_targets": [
>>> {
>>> "name": "default-placement",
>>> "tags": []
>>> }
>>> ],
>>> "default_placement": "default-placement",
>>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>>> }
>>> + echo Creating default zone
>>> Creating default zone
>>> + radosgw-admin zone set --rgw-zone=default
>>> zone id 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": "
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Your RGW doesn't think it's the master, and cannot connect to the master, thus the create fails. Daniel On 11/08/2016 06:36 PM, Andrei Mikhailovsky wrote: Hello I am having issues with creating buckets in radosgw. It started with an upgrade to version 10.2.x When I am creating a bucket I get the following error on the client side: boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request InvalidArgumentmy-new-bucket-31337tx2-0058225bae-994d148-default994d148-default-default The radosgw logs are (redacted): ### 2016-11-08 23:11:42.876862 7f026d953700 20 enqueued request req=0x7f02ba07b0e0 2016-11-08 23:11:42.876892 7f026d953700 20 RGWWQ: 2016-11-08 23:11:42.876897 7f026d953700 20 req: 0x7f02ba07b0e0 2016-11-08 23:11:42.876912 7f026d953700 10 allocated request req=0x7f02ba07b140 2016-11-08 23:11:42.876975 7f026b94f700 20 dequeued request req=0x7f02ba07b0e0 2016-11-08 23:11:42.876987 7f026b94f700 20 RGWWQ: empty 2016-11-08 23:11:42.877050 7f026b94f700 20 CONTENT_LENGTH=0 2016-11-08 23:11:42.877060 7f026b94f700 20 CONTEXT_DOCUMENT_ROOT=/var/www 2016-11-08 23:11:42.877062 7f026b94f700 20 CONTEXT_PREFIX= 2016-11-08 23:11:42.877063 7f026b94f700 20 DOCUMENT_ROOT=/var/www 2016-11-08 23:11:42.877081 7f026b94f700 20 FCGI_ROLE=RESPONDER 2016-11-08 23:11:42.877083 7f026b94f700 20 GATEWAY_INTERFACE=CGI/1.1 2016-11-08 23:11:42.877084 7f026b94f700 20 HTTP_ACCEPT_ENCODING=identity 2016-11-08 23:11:42.877086 7f026b94f700 20 HTTP_AUTHORIZATION=AWS XXXEDITEDXX:EDITEDXXXeWyiacaN26GcME 2016-11-08 23:11:42.877087 7f026b94f700 20 HTTP_DATE=Tue, 08 Nov 2016 23:11:37 GMT 2016-11-08 23:11:42.877088 7f026b94f700 20 HTTP_HOST=s3service.editedname.com 2016-11-08 23:11:42.877089 7f026b94f700 20 HTTP_USER_AGENT=Boto/2.38.0 Python/2.7.12 Linux/4.8.4-040804-generic 2016-11-08 23:11:42.877090 7f026b94f700 20 HTTPS=on 2016-11-08 23:11:42.877092 7f026b94f700 20 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin 2016-11-08 23:11:42.877093 7f026b94f700 20 proxy-nokeepalive=1 2016-11-08 23:11:42.877094 7f026b94f700 20 QUERY_STRING= 2016-11-08 23:11:42.877095 7f026b94f700 20 REMOTE_ADDR=192.168.169.91 2016-11-08 23:11:42.877096 7f026b94f700 20 REMOTE_PORT=45404 2016-11-08 23:11:42.877097 7f026b94f700 20 REQUEST_METHOD=PUT 2016-11-08 23:11:42.877098 7f026b94f700 20 REQUEST_SCHEME=https 2016-11-08 23:11:42.877099 7f026b94f700 20 REQUEST_URI=/my-new-bucket-31337/ 2016-11-08 23:11:42.877104 7f026b94f700 20 SCRIPT_FILENAME=proxy:fcgi://localhost:9000/my-new-bucket-31337/ 2016-11-08 23:11:42.877105 7f026b94f700 20 SCRIPT_NAME=/my-new-bucket-31337/ 2016-11-08 23:11:42.877107 7f026b94f700 20 SCRIPT_URI=https://s3service.editedname.com/my-new-bucket-31337/ 2016-11-08 23:11:42.877108 7f026b94f700 20 SCRIPT_URL=/my-new-bucket-31337/ 2016-11-08 23:11:42.877109 7f026b94f700 20 SERVER_ADDR=192.168.169.201 2016-11-08 23:11:42.877110 7f026b94f700 20 SERVER_ADMIN=and...@editedname.com 2016-11-08 23:11:42.877111 7f026b94f700 20 SERVER_NAME=s3service.editedname.com 2016-11-08 23:11:42.877112 7f026b94f700 20 SERVER_PORT=443 2016-11-08 23:11:42.877113 7f026b94f700 20 SERVER_PROTOCOL=HTTP/1.1 2016-11-08 23:11:42.877114 7f026b94f700 20 SERVER_SIGNATURE= 2016-11-08 23:11:42.877115 7f026b94f700 20 SERVER_SOFTWARE=Apache/2.4.18 (Ubuntu) 2016-11-08 23:11:42.877116 7f026b94f700 20 SSL_TLS_SNI=s3service.editedname.com 2016-11-08 23:11:42.877119 7f026b94f700 1 == starting new request req=0x7f02ba07b0e0 = 2016-11-08 23:11:42.877155 7f026b94f700 2 req 2:0.35::PUT /my-new-bucket-31337/::initializing for trans_id = tx2-0058225bae-994d148-default 2016-11-08 23:11:42.877175 7f026b94f700 10 rgw api priority: s3=5 s3website=4 2016-11-08 23:11:42.877179 7f026b94f700 10 host=s3service.editedname.com 2016-11-08 23:11:42.877199 7f026b94f700 20 subdomain= domain=s3service.editedname.com in_hosted_domain=1 in_hosted_domain_s3website=0 2016-11-08 23:11:42.877203 7f026b94f700 20 final domain/bucket subdomain= domain=s3service.editedname.com in_hosted_domain=1 in_hosted_domain_s3website=0 s->info.domain=s3service.editedname.com s->info.request_uri=/my-new-bucket-31337/ 2016-11-08 23:11:42.877277 7f026b94f700 20 get_handler handler=25RGWHandler_REST_Bucket_S3 2016-11-08 23:11:42.877286 7f026b94f700 10 handler=25RGWHandler_REST_Bucket_S3 2016-11-08 23:11:42.877291 7f026b94f700 2 req 2:0.000172:s3:PUT /my-new-bucket-31337/::getting op 1 2016-11-08 23:11:42.877326 7f026b94f700 10 op=27RGWCreateBucket_ObjStore_S3 2016-11-08 23:11:42.877334 7f026b94f700 2 req 2:0.000215:s3:PUT /my-new-bucket-31337/:create_bucket:authorizing 2016-11-08 23:11:42.877386 7f026b94f700 20 get_system_obj_state: rctx=0x7f026b94b7c0 obj=.users:XXXEDITEDXX state=0x7f02b70cdfe8 s->prefetch_data=0 2016-11-08 23:11:42.877403 7f026b94f700 10 cache get: name=.users+XXXEDITEDXX : miss 2016-11-08 23:11:42.877516 7f026b94f700 1 -- 192.168.168.201:0/3703211654 -->
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Orit, true.
yeah, all my servers are running 10.2.3-1xenial or 10.2.3-1trusty. I have a
small cluster and I always update all servers at once.
I don't have any Hammer releases of ceph anywhere on the network.
Is 10.2.4 out already? I didn't see an update package to that.
Thanks
Andrei
- Original Message -
> From: "Orit Wasserman" <owass...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users"
> <ceph-users@lists.ceph.com>
> Sent: Thursday, 10 November, 2016 13:58:32
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Thu, Nov 10, 2016 at 2:55 PM, Andrei Mikhailovsky <and...@arhont.com>
> wrote:
>> Orit,
>>
>> Here is what i've done just now:
>>
>> root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway stop
>>
>> (the above command was ran on both radosgw servers). Checked with ps and no
>> radosgw services were running. After that I've done:
>>
>>
>>
>> root@arh-ibstorage1-ib:~# ./ceph-zones-fix.sh
>> + RADOSGW_ADMIN=radosgw-admin
>> + echo Exercise initialization code
>> Exercise initialization code
>> + radosgw-admin user info --uid=foo
>> could not fetch user info: no user info saved
>> + echo Get default zonegroup
>> Get default zonegroup
>> + radosgw-admin zonegroup get --rgw-zonegroup=default
>> + sed s/"id":.*/"id": "default",/g
>> + sed s/"master_zone.*/"master_zone": "default",/g
>> + echo Get default zone
>> Get default zone
>> + radosgw-admin zone get --zone-id=default
>> + echo Creating realm
>> Creating realm
>> + radosgw-admin realm create --rgw-realm=london-ldex
>> ERROR: couldn't create realm london-ldex: (17) File exists
>> 2016-11-10 13:44:48.872839 7f87a13d9a00 0 ERROR creating new realm object
>> london-ldex: (17) File exists
>> + echo Creating default zonegroup
>> Creating default zonegroup
>> + radosgw-admin zonegroup set --rgw-zonegroup=default
>> {
>> "id": "default",
>> "name": "default",
>> "api_name": "",
>> "is_master": "true",
>> "endpoints": [],
>> "hostnames": [],
>> "hostnames_s3website": [],
>> "master_zone": "default",
>> "zones": [
>> {
>> "id": "default",
>> "name": "default",
>> "endpoints": [],
>> "log_meta": "false",
>> "log_data": "false",
>> "bucket_index_max_shards": 0,
>> "read_only": "false"
>> }
>> ],
>> "placement_targets": [
>> {
>> "name": "default-placement",
>> "tags": []
>> }
>> ],
>> "default_placement": "default-placement",
>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>> }
>> + echo Creating default zone
>> Creating default zone
>> + radosgw-admin zone set --rgw-zone=default
>> zone id 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": [
>> {
>> "key": "default-placement",
>> "val": {
>> "index_pool": ".rgw.buckets.index",
>> "data_pool": ".rgw.buckets",
>> "data_extra_pool": "defau
Re: [ceph-users] radosgw - http status 400 while creating a bucket
ot;,
> "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": [
> {
> "key": "default-placement",
> "val": {
> "index_pool": ".rgw.buckets.index",
> "data_pool": ".rgw.buckets",
> "data_extra_pool": "default.rgw.buckets.non-ec",
> "index_type": 0
> }
> }
> ],
> "metadata_heap": ".rgw.meta",
> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
> }
>
>
>
> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get --rgw-zonegroup=default
> {
> "id": "default",
> "name": "default",
> "api_name": "",
> "is_master": "true",
> "endpoints": [],
> "hostnames": [],
> "hostnames_s3website": [],
> "master_zone": "default",
> "zones": [
> {
> "id": "default",
> "name": "default",
> "endpoints": [],
> "log_meta": "false",
> "log_data": "false",
> "bucket_index_max_shards": 0,
> "read_only": "false"
> }
> ],
> "placement_targets": [
> {
> "name": "default-placement",
> "tags": []
> }
> ],
> "default_placement": "default-placement",
> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
> }
>
>
>
>
> As far as I can see, the master_zone is now set to default.
>
> Now I start the radosgw service:
>
>
> root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway start
> root@arh-ibstorage1-ib:~#
> root@arh-ibstorage1-ib:~#
> root@arh-ibstorage1-ib:~#
> root@arh-ibstorage1-ib:~#
> root@arh-ibstorage1-ib:~#
> root@arh-ibstorage1-ib:~# 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": [
> {
> "key": "default-placement",
> "val": {
> "index_pool": ".rgw.buckets.index",
> "data_pool": ".rgw.buckets",
> "data_extra_pool": "default.rgw.buckets.non-ec",
> "index_type": 0
> }
> }
> ],
> "metadata_heap": ".rgw.meta",
> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>
>
> root@arh-ibstorage1-ib:~# 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": "f
Re: [ceph-users] radosgw - http status 400 while creating a bucket
quot;,
"data_pool": ".rgw.buckets",
"data_extra_pool": "default.rgw.buckets.non-ec",
"index_type": 0
}
}
],
"metadata_heap": ".rgw.meta",
"realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
}
root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get --rgw-zonegroup=default
{
"id": "default",
"name": "default",
"api_name": "",
"is_master": "true",
"endpoints": [],
"hostnames": [],
"hostnames_s3website": [],
"master_zone": "default",
"zones": [
{
"id": "default",
"name": "default",
"endpoints": [],
"log_meta": "false",
"log_data": "false",
"bucket_index_max_shards": 0,
"read_only": "false"
}
],
"placement_targets": [
{
"name": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
"realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
}
As far as I can see, the master_zone is now set to default.
Now I start the radosgw service:
root@arh-ibstorage1-ib:~# service ceph-radosgw@radosgw.gateway start
root@arh-ibstorage1-ib:~#
root@arh-ibstorage1-ib:~#
root@arh-ibstorage1-ib:~#
root@arh-ibstorage1-ib:~#
root@arh-ibstorage1-ib:~#
root@arh-ibstorage1-ib:~# 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": [
{
"key": "default-placement",
"val": {
"index_pool": ".rgw.buckets.index",
"data_pool": ".rgw.buckets",
"data_extra_pool": "default.rgw.buckets.non-ec",
"index_type": 0
}
}
],
"metadata_heap": ".rgw.meta",
"realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
root@arh-ibstorage1-ib:~# 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": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
"realm_id": ""
}
As you can see from above, the realm_id and the master_zone have reverted back
to being blank! Crazy!!!
Andrei
- Original Message -
> From: "Orit Wasserman" <owass...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users"
> <ceph-users@lists.ceph.com>
> Sent: Thursday, 10 November, 2016 13:36:01
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Thu, Nov 10, 2016 at 2:24 PM, Andrei Mikhailovsky <and...@arhont.com>
> wrote:
>>
>> Hi Orit,
>>
>> Thanks for the links.
>>
>> I've had a look at the link that you've sent
>> http://l
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Orit,
I have two radosgw services running on two physical servers within the same
zone. This was done to minimise downtime while the maintenance is done. The
http proxy sits on top and balances the links. The clients connect to http
proxy.
I will double check, but I think I did shut down both services before running
the script. I will run it again to make sure.
Andrei
- Original Message -
> From: "Orit Wasserman" <owass...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "Yoann Moulin" <yoann.mou...@epfl.ch>, "ceph-users"
> <ceph-users@lists.ceph.com>
> Sent: Thursday, 10 November, 2016 13:36:01
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Thu, Nov 10, 2016 at 2:24 PM, Andrei Mikhailovsky <and...@arhont.com>
> wrote:
>>
>> Hi Orit,
>>
>> Thanks for the links.
>>
>> I've had a look at the link that you've sent
>> http://lists.ceph.com/pipermail/ceph-users-ceph.com/2016-July/011157.html and
>> followed the instructions. Created the script as depicted in the email.
>> Changed
>> the realm name to something relevant. The script ran without any errors. I've
>> restarted radosgw services on both servers, but I am still unable to create
>> buckets. I am getting exactly the same error from the client:
>>
>
> So you have two radosgw running on different servers, on the same zone
> (default) and on the same rados cluster?
> Are both gateways from the same version?
> Did you shutdown both gateway when you run the script?
>
>>
>> S3ResponseError: 400 Bad Request
>> > encoding="UTF-8"?>InvalidArgumentmy-new-bucket-31337tx3-00582472a4-995ee8c-default995ee8c-default-default
>>
>>
>> I can delete a bucket, but I can't create a new one.
>>
>>
>> What I did notice is that after running the script and getting the zonegroup
>> info, I do see both the master_zone and the realm_id fields are set:
>>
>>
>>
>> "master_zone": "default",
>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>>
>>
>> However, after I restart radosgw service, they go back to being blank:
>>
>>
>> "master_zone": "",
>> "realm_id": ""
>>
>>
>> In any case, creation of buckets doesn't work either way.
>>
>> Cheers
>>
>>
>> Andrei
>>
>>
>> - Original Message -
>>> From: "Orit Wasserman" <owass...@redhat.com>
>>> To: "Yoann Moulin" <yoann.mou...@epfl.ch>
>>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>>> Sent: Thursday, 10 November, 2016 10:04:46
>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>>
>>> On Wed, Nov 9, 2016 at 10:20 PM, Yoann Moulin <yoann.mou...@epfl.ch> wrote:
>>>> Hello,
>>>>
>>>>> many thanks for your help. I've tried setting the zone to master,
>>>>> followed by
>>>>> the period update --commit command. This is what i've had:
>>>>
>>>> maybe it's related to this issue :
>>>>
>>>> http://tracker.ceph.com/issues/16839 (fixe in Jewel 10.2.3)
>>>>
>>>> or this one :
>>>>
>>>> http://tracker.ceph.com/issues/17239
>>>>
>>>> the "id" of the zonegroup shouldn't be "default" but an uuid afaik
>>>>
>>>> Best regards
>>>>
>>>> Yoann Moulin
>>>>
>>>>> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get
>>>>> --rgw-zonegroup=default
>>>>> {
>>>>> "id": "default",
>>>>> "name": "default",
>>>>> "api_name": "",
>>>>> "is_master": "true",
>>>>> "endpoints": [],
>>>>> "hostnames": [],
>>>>> "hostnames_s3website": [],
>>>>> "master_zone": "default",
>>>>> "zones": [
>>>>> {
>>>>> "id": "default",
>>>>> "name": "default",
>>>>> "endpoints": [],
>>>>> "log_meta": "false",
>>>>>
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Orit,
Thanks for the links.
I've had a look at the link that you've sent
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2016-July/011157.html and
followed the instructions. Created the script as depicted in the email. Changed
the realm name to something relevant. The script ran without any errors. I've
restarted radosgw services on both servers, but I am still unable to create
buckets. I am getting exactly the same error from the client:
S3ResponseError: 400 Bad Request
InvalidArgumentmy-new-bucket-31337tx3-00582472a4-995ee8c-default995ee8c-default-default
I can delete a bucket, but I can't create a new one.
What I did notice is that after running the script and getting the zonegroup
info, I do see both the master_zone and the realm_id fields are set:
"master_zone": "default",
"realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
However, after I restart radosgw service, they go back to being blank:
"master_zone": "",
"realm_id": ""
In any case, creation of buckets doesn't work either way.
Cheers
Andrei
- Original Message -
> From: "Orit Wasserman" <owass...@redhat.com>
> To: "Yoann Moulin" <yoann.mou...@epfl.ch>
> Cc: "ceph-users" <ceph-users@lists.ceph.com>
> Sent: Thursday, 10 November, 2016 10:04:46
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Wed, Nov 9, 2016 at 10:20 PM, Yoann Moulin <yoann.mou...@epfl.ch> wrote:
>> Hello,
>>
>>> many thanks for your help. I've tried setting the zone to master, followed
>>> by
>>> the period update --commit command. This is what i've had:
>>
>> maybe it's related to this issue :
>>
>> http://tracker.ceph.com/issues/16839 (fixe in Jewel 10.2.3)
>>
>> or this one :
>>
>> http://tracker.ceph.com/issues/17239
>>
>> the "id" of the zonegroup shouldn't be "default" but an uuid afaik
>>
>> Best regards
>>
>> Yoann Moulin
>>
>>> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get
>>> --rgw-zonegroup=default
>>> {
>>> "id": "default",
>>> "name": "default",
>>> "api_name": "",
>>> "is_master": "true",
>>> "endpoints": [],
>>> "hostnames": [],
>>> "hostnames_s3website": [],
>>> "master_zone": "default",
>>> "zones": [
>>> {
>>> "id": "default",
>>> "name": "default",
>>> "endpoints": [],
>>> "log_meta": "false",
>>> "log_data": "false",
>>> "bucket_index_max_shards": 0,
>>> "read_only": "false"
>>> }
>>> ],
>>> "placement_targets": [
>>> {
>>> "name": "default-placement",
>>> "tags": []
>>> }
>>> ],
>>> "default_placement": "default-placement",
>>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>>> }
>>>
>>>
>>> root@arh-ibstorage1-ib:~# radosgw-admin period update --commit
>>> cannot commit period: period does not have a master zone of a master
>>> zonegroup
>>> failed to commit period: (22) Invalid argument
>>>
>>>
>
> This is issue http://tracker.ceph.com/issues/17364 (I am working on it
> at he moment).
>
> Do the same procedure as before without the period update --commit command,
> it should fix the master zone problem.
> see also
> http://lists.ceph.com/pipermail/ceph-users-ceph.com/2016-July/011157.html
>
> This looks like an upgraded system (the id equals the name after an upgrade).
>
> Orit
>
>>> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get
>>> --rgw-zonegroup=default
>>> {
>>> "id": "default",
>>> "name": "default",
>>> "api_name": "",
>>> "is_master": "true",
>>> "endpoints": [],
>>> "hostnames": [],
>>> "hostnames_s3website": [],
>>> "master_zone": "",
>>>
Re: [ceph-users] radosgw - http status 400 while creating a bucket
On Wed, Nov 9, 2016 at 10:20 PM, Yoann Moulin <yoann.mou...@epfl.ch> wrote:
> Hello,
>
>> many thanks for your help. I've tried setting the zone to master, followed
>> by the period update --commit command. This is what i've had:
>
> maybe it's related to this issue :
>
> http://tracker.ceph.com/issues/16839 (fixe in Jewel 10.2.3)
>
> or this one :
>
> http://tracker.ceph.com/issues/17239
>
> the "id" of the zonegroup shouldn't be "default" but an uuid afaik
>
> Best regards
>
> Yoann Moulin
>
>> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get --rgw-zonegroup=default
>> {
>> "id": "default",
>> "name": "default",
>> "api_name": "",
>> "is_master": "true",
>> "endpoints": [],
>> "hostnames": [],
>> "hostnames_s3website": [],
>> "master_zone": "default",
>> "zones": [
>> {
>> "id": "default",
>> "name": "default",
>> "endpoints": [],
>> "log_meta": "false",
>> "log_data": "false",
>> "bucket_index_max_shards": 0,
>> "read_only": "false"
>> }
>> ],
>> "placement_targets": [
>> {
>> "name": "default-placement",
>> "tags": []
>> }
>> ],
>> "default_placement": "default-placement",
>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>> }
>>
>>
>> root@arh-ibstorage1-ib:~# radosgw-admin period update --commit
>> cannot commit period: period does not have a master zone of a master
>> zonegroup
>> failed to commit period: (22) Invalid argument
>>
>>
This is issue http://tracker.ceph.com/issues/17364 (I am working on it
at he moment).
Do the same procedure as before without the period update --commit command,
it should fix the master zone problem.
see also
http://lists.ceph.com/pipermail/ceph-users-ceph.com/2016-July/011157.html
This looks like an upgraded system (the id equals the name after an upgrade).
Orit
>> root@arh-ibstorage1-ib:~# 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": "default-placement",
>> "tags": []
>> }
>> ],
>> "default_placement": "default-placement",
>> "realm_id": ""
>> }
>>
>>
>>
>>
>>
>> The strange thing as you can see, following the "radosgw-admin period update
>> --commit" command, the master_zone and the realm_id values reset to blank.
>> What could be causing this?
>>
>> Here is my ceph infrastructure setup, perhaps it will help with finding the
>> issue?:
>>
>> ceph osd and mon servers:
>> arh-ibstorage1-ib (also radosgw server)
>> arh-ibstorage2-ib (also radosgw server)
>> arh-ibstorage3-ib
>>
>> ceph mon server:
>> arh-cloud13-ib
>>
>>
>>
>> Thus, overall, i have 4 mon servers, 3 osd servers and 2 radosgw servers
>>
>> Thanks
>>
>>
>>
>> - Original Message -
>>> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
>>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>>> Sent: Wednesd
Re: [ceph-users] radosgw - http status 400 while creating a bucket
***bump***
this is pretty broken and urgent. thanks
- Original Message -
> From: "Andrei Mikhailovsky" <and...@arhont.com>
> To: "Yoann Moulin" <yoann.mou...@epfl.ch>
> Cc: "ceph-users" <ceph-users@lists.ceph.com>
> Sent: Wednesday, 9 November, 2016 23:27:17
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> Hi Yoann,
>
> I am running 10.2.3 on all nodes.
>
> Andrei
>
> - Original Message -
>> From: "Yoann Moulin" <yoann.mou...@epfl.ch>
>> To: "ceph-users" <ceph-users@lists.ceph.com>
>> Sent: Wednesday, 9 November, 2016 21:20:45
>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>
>> Hello,
>>
>>> many thanks for your help. I've tried setting the zone to master, followed
>>> by
>>> the period update --commit command. This is what i've had:
>>
>> maybe it's related to this issue :
>>
>> http://tracker.ceph.com/issues/16839 (fixe in Jewel 10.2.3)
>>
>> or this one :
>>
>> http://tracker.ceph.com/issues/17239
>>
>> the "id" of the zonegroup shouldn't be "default" but an uuid afaik
>>
>> Best regards
>>
>> Yoann Moulin
>>
>>> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get
>>> --rgw-zonegroup=default
>>> {
>>> "id": "default",
>>> "name": "default",
>>> "api_name": "",
>>> "is_master": "true",
>>> "endpoints": [],
>>> "hostnames": [],
>>> "hostnames_s3website": [],
>>> "master_zone": "default",
>>> "zones": [
>>> {
>>> "id": "default",
>>> "name": "default",
>>> "endpoints": [],
>>> "log_meta": "false",
>>> "log_data": "false",
>>> "bucket_index_max_shards": 0,
>>> "read_only": "false"
>>> }
>>> ],
>>> "placement_targets": [
>>> {
>>> "name": "default-placement",
>>> "tags": []
>>> }
>>> ],
>>> "default_placement": "default-placement",
>>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>>> }
>>>
>>>
>>> root@arh-ibstorage1-ib:~# radosgw-admin period update --commit
>>> cannot commit period: period does not have a master zone of a master
>>> zonegroup
>>> failed to commit period: (22) Invalid argument
>>>
>>>
>>> root@arh-ibstorage1-ib:~# 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": "default-placement",
>>> "tags": []
>>> }
>>> ],
>>> "default_placement": "default-placement",
>>> "realm_id": ""
>>> }
>>>
>>>
>>>
>>>
>>>
>>> The strange thing as you can see, following the "radosgw-admin period update
>>> --commit" command, the master_zone and the realm_id values reset to blank.
>>> What
>>> could be ca
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Yoann,
I am running 10.2.3 on all nodes.
Andrei
- Original Message -
> From: "Yoann Moulin" <yoann.mou...@epfl.ch>
> To: "ceph-users" <ceph-users@lists.ceph.com>
> Sent: Wednesday, 9 November, 2016 21:20:45
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> Hello,
>
>> many thanks for your help. I've tried setting the zone to master, followed by
>> the period update --commit command. This is what i've had:
>
> maybe it's related to this issue :
>
> http://tracker.ceph.com/issues/16839 (fixe in Jewel 10.2.3)
>
> or this one :
>
> http://tracker.ceph.com/issues/17239
>
> the "id" of the zonegroup shouldn't be "default" but an uuid afaik
>
> Best regards
>
> Yoann Moulin
>
>> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get --rgw-zonegroup=default
>> {
>> "id": "default",
>> "name": "default",
>> "api_name": "",
>> "is_master": "true",
>> "endpoints": [],
>> "hostnames": [],
>> "hostnames_s3website": [],
>> "master_zone": "default",
>> "zones": [
>> {
>> "id": "default",
>> "name": "default",
>> "endpoints": [],
>> "log_meta": "false",
>> "log_data": "false",
>> "bucket_index_max_shards": 0,
>> "read_only": "false"
>> }
>> ],
>> "placement_targets": [
>> {
>> "name": "default-placement",
>> "tags": []
>> }
>> ],
>> "default_placement": "default-placement",
>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>> }
>>
>>
>> root@arh-ibstorage1-ib:~# radosgw-admin period update --commit
>> cannot commit period: period does not have a master zone of a master
>> zonegroup
>> failed to commit period: (22) Invalid argument
>>
>>
>> root@arh-ibstorage1-ib:~# 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": "default-placement",
>> "tags": []
>> }
>> ],
>> "default_placement": "default-placement",
>> "realm_id": ""
>> }
>>
>>
>>
>>
>>
>> The strange thing as you can see, following the "radosgw-admin period update
>> --commit" command, the master_zone and the realm_id values reset to blank.
>> What
>> could be causing this?
>>
>> Here is my ceph infrastructure setup, perhaps it will help with finding the
>> issue?:
>>
>> ceph osd and mon servers:
>> arh-ibstorage1-ib (also radosgw server)
>> arh-ibstorage2-ib (also radosgw server)
>> arh-ibstorage3-ib
>>
>> ceph mon server:
>> arh-cloud13-ib
>>
>>
>>
>> Thus, overall, i have 4 mon servers, 3 osd servers and 2 radosgw servers
>>
>> Thanks
>>
>>
>>
>> - Original Message -
>>> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
>>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>>> Sent: Wednesday, 9 November, 2016 17:12:30
>>> Subject: Re: [ce
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hello,
> many thanks for your help. I've tried setting the zone to master, followed by
> the period update --commit command. This is what i've had:
maybe it's related to this issue :
http://tracker.ceph.com/issues/16839 (fixe in Jewel 10.2.3)
or this one :
http://tracker.ceph.com/issues/17239
the "id" of the zonegroup shouldn't be "default" but an uuid afaik
Best regards
Yoann Moulin
> root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get --rgw-zonegroup=default
> {
> "id": "default",
> "name": "default",
> "api_name": "",
> "is_master": "true",
> "endpoints": [],
> "hostnames": [],
> "hostnames_s3website": [],
> "master_zone": "default",
> "zones": [
> {
> "id": "default",
> "name": "default",
> "endpoints": [],
> "log_meta": "false",
> "log_data": "false",
> "bucket_index_max_shards": 0,
> "read_only": "false"
> }
> ],
> "placement_targets": [
> {
> "name": "default-placement",
> "tags": []
> }
> ],
> "default_placement": "default-placement",
> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
> }
>
>
> root@arh-ibstorage1-ib:~# radosgw-admin period update --commit
> cannot commit period: period does not have a master zone of a master zonegroup
> failed to commit period: (22) Invalid argument
>
>
> root@arh-ibstorage1-ib:~# 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": "default-placement",
> "tags": []
> }
> ],
> "default_placement": "default-placement",
> "realm_id": ""
> }
>
>
>
>
>
> The strange thing as you can see, following the "radosgw-admin period update
> --commit" command, the master_zone and the realm_id values reset to blank.
> What could be causing this?
>
> Here is my ceph infrastructure setup, perhaps it will help with finding the
> issue?:
>
> ceph osd and mon servers:
> arh-ibstorage1-ib (also radosgw server)
> arh-ibstorage2-ib (also radosgw server)
> arh-ibstorage3-ib
>
> ceph mon server:
> arh-cloud13-ib
>
>
>
> Thus, overall, i have 4 mon servers, 3 osd servers and 2 radosgw servers
>
> Thanks
>
>
>
> - Original Message -
>> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>> Sent: Wednesday, 9 November, 2016 17:12:30
>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>
>> On Wed, Nov 9, 2016 at 1:30 AM, Andrei Mikhailovsky <and...@arhont.com>
>> wrote:
>>> Hi Yehuda,
>>>
>>> just tried to run the command to set the master_zone to default followed by
>>> the
>>> bucket create without doing the restart and I still have the same error on
>>> the
>>> client:
>>>
>>> >> encoding="UTF-8"?>InvalidArgumentmy-new-bucket-31337tx00010-005822ebbd-9951ad8-default9951ad8-default-default
>>>
>>
>> After setting the master zone, try running:
>>
>> $ radosgw-admin period update --commit
>>
>> Yehuda
>>
>>>
>>> Andrei
>>>
>>> - Original Mess
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Yehuda,
many thanks for your help. I've tried setting the zone to master, followed by
the period update --commit command. This is what i've had:
root@arh-ibstorage1-ib:~# radosgw-admin zonegroup get --rgw-zonegroup=default
{
"id": "default",
"name": "default",
"api_name": "",
"is_master": "true",
"endpoints": [],
"hostnames": [],
"hostnames_s3website": [],
"master_zone": "default",
"zones": [
{
"id": "default",
"name": "default",
"endpoints": [],
"log_meta": "false",
"log_data": "false",
"bucket_index_max_shards": 0,
"read_only": "false"
}
],
"placement_targets": [
{
"name": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
"realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
}
root@arh-ibstorage1-ib:~# radosgw-admin period update --commit
cannot commit period: period does not have a master zone of a master zonegroup
failed to commit period: (22) Invalid argument
root@arh-ibstorage1-ib:~# 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": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
"realm_id": ""
}
The strange thing as you can see, following the "radosgw-admin period update
--commit" command, the master_zone and the realm_id values reset to blank. What
could be causing this?
Here is my ceph infrastructure setup, perhaps it will help with finding the
issue?:
ceph osd and mon servers:
arh-ibstorage1-ib (also radosgw server)
arh-ibstorage2-ib (also radosgw server)
arh-ibstorage3-ib
ceph mon server:
arh-cloud13-ib
Thus, overall, i have 4 mon servers, 3 osd servers and 2 radosgw servers
Thanks
- Original Message -
> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "ceph-users" <ceph-users@lists.ceph.com>
> Sent: Wednesday, 9 November, 2016 17:12:30
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Wed, Nov 9, 2016 at 1:30 AM, Andrei Mikhailovsky <and...@arhont.com> wrote:
>> Hi Yehuda,
>>
>> just tried to run the command to set the master_zone to default followed by
>> the
>> bucket create without doing the restart and I still have the same error on
>> the
>> client:
>>
>> > encoding="UTF-8"?>InvalidArgumentmy-new-bucket-31337tx00010-005822ebbd-9951ad8-default9951ad8-default-default
>>
>
> After setting the master zone, try running:
>
> $ radosgw-admin period update --commit
>
> Yehuda
>
>>
>> Andrei
>>
>> - Original Message -
>>> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
>>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>>> Sent: Wednesday, 9 November, 2016 01:13:48
>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>>
>>> On Tue, Nov 8, 2016 at 5:05 PM, Andrei Mikhailovsky <and...@arhont.com>
>>> wrote:
>>>> Hi Yehuda,
>>>>
>>>> I don't have a multizone setup. The radosgw service was configured about
>>>> two
>>>> years ago according to the documentation on ceph.com and haven't changed
>>>> with
>>>> numerous version updates. All was working okay until i've upgraded to
>>>> version
>&g
Re: [ceph-users] radosgw - http status 400 while creating a bucket
On Wed, Nov 9, 2016 at 1:30 AM, Andrei Mikhailovsky <and...@arhont.com> wrote:
> Hi Yehuda,
>
> just tried to run the command to set the master_zone to default followed by
> the bucket create without doing the restart and I still have the same error
> on the client:
>
> encoding="UTF-8"?>InvalidArgumentmy-new-bucket-31337tx00010-005822ebbd-9951ad8-default9951ad8-default-default
>
After setting the master zone, try running:
$ radosgw-admin period update --commit
Yehuda
>
> Andrei
>
> - Original Message -
>> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>> Sent: Wednesday, 9 November, 2016 01:13:48
>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>
>> On Tue, Nov 8, 2016 at 5:05 PM, Andrei Mikhailovsky <and...@arhont.com>
>> wrote:
>>> Hi Yehuda,
>>>
>>> I don't have a multizone setup. The radosgw service was configured about two
>>> years ago according to the documentation on ceph.com and haven't changed
>>> with
>>> numerous version updates. All was working okay until i've upgraded to
>>> version
>>> 10.2.x.
>>>
>>> Could you please point me in the right direction what exactly needs to be
>>> done?
>>>
>>>
>>> # 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": "default-placement",
>>> "tags": []
>>> }
>>> ],
>>> "default_placement": "default-placement",
>>> "realm_id": ""
>>> }
>>
>> Try:
>>
>> $ radosgw-admin zonegroup get --rgw-zonegroup=default > zonegroup.json
>>
>> ... modify the master_zone to be "default"
>>
>> $ radosgw-admin zonegroup set --rgw-zonegroup=default < zonegroup.json
>>
>> (restart radosgw)
>>
>> Yehuda
>>
>>>
>>>
>>>
>>> # 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": [
>>> {
>>> "key": "default-placement",
>>> "val": {
>>> "index_pool": ".rgw.buckets.index",
>>> "data_pool": ".rgw.buckets",
>>> "data_extra_pool": "default.rgw.buckets.non-ec",
>>> "index_type": 0
>>> }
>>> }
>>> ],
>>> "metad
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Yehuda,
just tried to run the command to set the master_zone to default followed by the
bucket create without doing the restart and I still have the same error on the
client:
InvalidArgumentmy-new-bucket-31337tx00010-005822ebbd-9951ad8-default9951ad8-default-default
Andrei
- Original Message -
> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "ceph-users" <ceph-users@lists.ceph.com>
> Sent: Wednesday, 9 November, 2016 01:13:48
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Tue, Nov 8, 2016 at 5:05 PM, Andrei Mikhailovsky <and...@arhont.com> wrote:
>> Hi Yehuda,
>>
>> I don't have a multizone setup. The radosgw service was configured about two
>> years ago according to the documentation on ceph.com and haven't changed with
>> numerous version updates. All was working okay until i've upgraded to version
>> 10.2.x.
>>
>> Could you please point me in the right direction what exactly needs to be
>> done?
>>
>>
>> # 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": "default-placement",
>> "tags": []
>> }
>> ],
>> "default_placement": "default-placement",
>> "realm_id": ""
>> }
>
> Try:
>
> $ radosgw-admin zonegroup get --rgw-zonegroup=default > zonegroup.json
>
> ... modify the master_zone to be "default"
>
> $ radosgw-admin zonegroup set --rgw-zonegroup=default < zonegroup.json
>
> (restart radosgw)
>
> Yehuda
>
>>
>>
>>
>> # 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": [
>> {
>> "key": "default-placement",
>> "val": {
>> "index_pool": ".rgw.buckets.index",
>> "data_pool": ".rgw.buckets",
>> "data_extra_pool": "default.rgw.buckets.non-ec",
>> "index_type": 0
>> }
>> }
>> ],
>> "metadata_heap": ".rgw.meta",
>> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
>> }
>>
>>
>>
>> Thanks
>>
>>
>>
>> - Original Message -
>>> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
>>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>>> Sent: Wednesday, 9 November, 2016 00:48:50
>>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>>
>>> On Tue, Nov 8, 2016 at 3:36 PM, A
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Yehuda,
I've tried that and after performed:
# radosgw-admin zonegroup get --rgw-zonegroup=default
{
"id": "default",
"name": "default",
"api_name": "",
"is_master": "true",
"endpoints": [],
"hostnames": [],
"hostnames_s3website": [],
"master_zone": "default",
"zones": [
{
"id": "default",
"name": "default",
"endpoints": [],
"log_meta": "false",
"log_data": "false",
"bucket_index_max_shards": 0,
"read_only": "false"
}
],
"placement_targets": [
{
"name": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
"realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
}
As you can see, the master_zone is now set to default. However, after
performing radosgw restart, the master_zone went back to being "". What else
should I try?
Thanks
Andrei
- Original Message -
> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "ceph-users" <ceph-users@lists.ceph.com>
> Sent: Wednesday, 9 November, 2016 01:13:48
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Tue, Nov 8, 2016 at 5:05 PM, Andrei Mikhailovsky <and...@arhont.com> wrote:
>> Hi Yehuda,
>>
>> I don't have a multizone setup. The radosgw service was configured about two
>> years ago according to the documentation on ceph.com and haven't changed with
>> numerous version updates. All was working okay until i've upgraded to version
>> 10.2.x.
>>
>> Could you please point me in the right direction what exactly needs to be
>> done?
>>
>>
>> # 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": "default-placement",
>> "tags": []
>> }
>> ],
>> "default_placement": "default-placement",
>> "realm_id": ""
>> }
>
> Try:
>
> $ radosgw-admin zonegroup get --rgw-zonegroup=default > zonegroup.json
>
> ... modify the master_zone to be "default"
>
> $ radosgw-admin zonegroup set --rgw-zonegroup=default < zonegroup.json
>
> (restart radosgw)
>
> Yehuda
>
>>
>>
>>
>> # 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": [
>> {
>> "key": "default-placement",
>> "val": {
>> &quo
Re: [ceph-users] radosgw - http status 400 while creating a bucket
On Tue, Nov 8, 2016 at 5:05 PM, Andrei Mikhailovsky <and...@arhont.com> wrote:
> Hi Yehuda,
>
> I don't have a multizone setup. The radosgw service was configured about two
> years ago according to the documentation on ceph.com and haven't changed with
> numerous version updates. All was working okay until i've upgraded to version
> 10.2.x.
>
> Could you please point me in the right direction what exactly needs to be
> done?
>
>
> # 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": "default-placement",
> "tags": []
> }
> ],
> "default_placement": "default-placement",
> "realm_id": ""
> }
Try:
$ radosgw-admin zonegroup get --rgw-zonegroup=default > zonegroup.json
... modify the master_zone to be "default"
$ radosgw-admin zonegroup set --rgw-zonegroup=default < zonegroup.json
(restart radosgw)
Yehuda
>
>
>
> # 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": [
> {
> "key": "default-placement",
> "val": {
> "index_pool": ".rgw.buckets.index",
> "data_pool": ".rgw.buckets",
> "data_extra_pool": "default.rgw.buckets.non-ec",
> "index_type": 0
> }
> }
> ],
> "metadata_heap": ".rgw.meta",
> "realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
> }
>
>
>
> Thanks
>
>
>
> - Original Message -
>> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
>> To: "Andrei Mikhailovsky" <and...@arhont.com>
>> Cc: "ceph-users" <ceph-users@lists.ceph.com>
>> Sent: Wednesday, 9 November, 2016 00:48:50
>> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
>
>> On Tue, Nov 8, 2016 at 3:36 PM, Andrei Mikhailovsky <and...@arhont.com>
>> wrote:
>>> Hello
>>>
>>> I am having issues with creating buckets in radosgw. It started with an
>>> upgrade to version 10.2.x
>>>
>>> When I am creating a bucket I get the following error on the client side:
>>>
>>>
>>> boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request
>>> >> encoding="UTF-8"?>InvalidArgumentmy-new-bucket-31337tx2-0058225bae-994d148-default994d148-default-default
>>>
>>>
>>> The radosgw logs are (redacted):
>>>
>>> ###
>>>
>>> 2016-11-08 23:11:42.876862 7f026d953700 20 enqueued request
>>> req=0x7f02ba07b0e0
>>> 2016-11-08 23:11:42.876892 7f026d953700 20 RGWWQ:
>>> 2016-11-08 23:11:42.876897 7f026d953700 20 req: 0x7f02ba07b0e0
>>> 2016-11-08 23:11:42.876912 7f026d953700 10 allocated request
>>> req=0x7f02ba07b140
>>> 2016-1
Re: [ceph-users] radosgw - http status 400 while creating a bucket
Hi Yehuda,
I don't have a multizone setup. The radosgw service was configured about two
years ago according to the documentation on ceph.com and haven't changed with
numerous version updates. All was working okay until i've upgraded to version
10.2.x.
Could you please point me in the right direction what exactly needs to be done?
# 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": "default-placement",
"tags": []
}
],
"default_placement": "default-placement",
"realm_id": ""
}
# 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": [
{
"key": "default-placement",
"val": {
"index_pool": ".rgw.buckets.index",
"data_pool": ".rgw.buckets",
"data_extra_pool": "default.rgw.buckets.non-ec",
"index_type": 0
}
}
],
"metadata_heap": ".rgw.meta",
"realm_id": "5b41b1b2-0f92-463d-b582-07552f83e66c"
}
Thanks
- Original Message -
> From: "Yehuda Sadeh-Weinraub" <yeh...@redhat.com>
> To: "Andrei Mikhailovsky" <and...@arhont.com>
> Cc: "ceph-users" <ceph-users@lists.ceph.com>
> Sent: Wednesday, 9 November, 2016 00:48:50
> Subject: Re: [ceph-users] radosgw - http status 400 while creating a bucket
> On Tue, Nov 8, 2016 at 3:36 PM, Andrei Mikhailovsky <and...@arhont.com> wrote:
>> Hello
>>
>> I am having issues with creating buckets in radosgw. It started with an
>> upgrade to version 10.2.x
>>
>> When I am creating a bucket I get the following error on the client side:
>>
>>
>> boto.exception.S3ResponseError: S3ResponseError: 400 Bad Request
>> > encoding="UTF-8"?>InvalidArgumentmy-new-bucket-31337tx2-0058225bae-994d148-default994d148-default-default
>>
>>
>> The radosgw logs are (redacted):
>>
>> ###
>>
>> 2016-11-08 23:11:42.876862 7f026d953700 20 enqueued request
>> req=0x7f02ba07b0e0
>> 2016-11-08 23:11:42.876892 7f026d953700 20 RGWWQ:
>> 2016-11-08 23:11:42.876897 7f026d953700 20 req: 0x7f02ba07b0e0
>> 2016-11-08 23:11:42.876912 7f026d953700 10 allocated request
>> req=0x7f02ba07b140
>> 2016-11-08 23:11:42.876975 7f026b94f700 20 dequeued request
>> req=0x7f02ba07b0e0
>> 2016-11-08 23:11:42.876987 7f026b94f700 20 RGWWQ: empty
>> 2016-11-08 23:11:42.877050 7f026b94f700 20 CONTENT_LENGTH=0
>> 2016-11-08 23:11:42.877060 7f026b94f700 20 CONTEXT_DOCUMENT_ROOT=/var/www
>> 2016-11-08 23:11:42.877062 7f026b94f700 20 CONTEXT_PREFIX=
>> 2016-11-08 23:11:42.877063 7f026b94f700 20 DOCUMENT_ROOT=/var/www
>> 2016-11-08 23:11:42.877081 7f026b94f700 20 FCGI_ROLE=RESPONDER
>> 2016-11-08 23:11:42.877083 7f026b94f700 20 GATEWAY_INTERFACE=CGI/1.1
>> 2016-11-08 23:11:42.877084 7f026b94f700 20 HTTP_ACCEPT_ENCODING=identity
>> 2016-11-08 23:11:42.877086 7f026b94f700 20 HTTP_AUTHORIZATION=AWS
>> XXXEDITEDXX:EDITEDXXXeWyiacaN26GcME
>> 2016-11-08 23:11:42.877087 7f026b94f700 20 HTTP
