Hi Cephers,
I upgraded to Jewel and noted the is massive radosgw multisite rework
in the release notes.
Can Jewel radosgw be configured to present existing Hammer buckets?
On a test system, jewel didn't recognise my Hammer buckets;
Hammer used pools .rgw.*
Jewel created by default: .rgw.root an
On Sat, Apr 23, 2016 at 6:22 AM, Richard Chan
wrote:
> Hi Cephers,
>
> I upgraded to Jewel and noted the is massive radosgw multisite rework
> in the release notes.
>
> Can Jewel radosgw be configured to present existing Hammer buckets?
> On a test system, jewel didn't recognise my Hammer buckets
On 23-04-16 18:17, Yehuda Sadeh-Weinraub wrote:
> On Sat, Apr 23, 2016 at 6:22 AM, Richard Chan
> wrote:
>> Hi Cephers,
>>
>> I upgraded to Jewel and noted the is massive radosgw multisite rework
>> in the release notes.
>>
>> Can Jewel radosgw be configured to present existing Hammer buckets?
>>
Hi Yehuda
I created a test 3xVM setup with Hammer and one radosgw on the (separate)
admin node; creating one user and buckets.
I upgraded the VMs to jewel and created a new radosgw on one of the nodes.
The object store didn't seem to survive the upgrade
# radosgw-admin user info --uid=testuser
(sorry for resubmission, adding ceph-users)
On Mon, Apr 25, 2016 at 9:47 AM, Richard Chan
wrote:
> Hi Yehuda
>
> I created a test 3xVM setup with Hammer and one radosgw on the (separate)
> admin node; creating one user and buckets.
>
> I upgraded the VMs to jewel and created a new radosgw on one
> > How do you actually do that?
>
> What does 'radosgw-admin zone get' return?
>
> Yehuda
>
[root@node1 ceph]# radosgw-admin zone get
unable to initialize zone: (2) No such file or directory
(I don't have any rgw configuration in /etc/ceph/ceph.conf; this is from a
clean
ceph-deploy rgw create
I managed to reproduce the issue, and there seem to be multiple
problems. Specifically we have an issue when upgrading a default
cluster that hasn't had a zone (and region) explicitly configured
before. There is another bug that I found
(http://tracker.ceph.com/issues/15597) that makes things even
Quick questions:
1. Should this script be run on a pre-Jewel setup (e.g. revert test VMs) or
*after* Jewel attempted to read the no-zone/no-region Hammer and created
the default.* pools?
2. Should the radosgw daemon be running when executing the script?
Thanks!
On Tue, Apr 26, 2016 at 8:06
Result:
1. user and buckets recognised;
2. radosgw-admin bucket list --bucket test.1
shows objects
but
3. s3cmd cannot list contents of buckets
# s3cmd -c jewel.cfg ls
2016-04-25 15:57 s3://test.1
2016-04-25 15:58 s3://test.2
# s3cmd -c jewel.cfg ls s3://test.1/
ERROR: S3 error: None
s3cmd -c
Also s3cmd is unable to create new buckets:
# s3cmd -c jewel.cfg mb s3://test.3
ERROR: S3 error: None
On Tue, Apr 26, 2016 at 8:06 AM, Yehuda Sadeh-Weinraub
wrote:
> I managed to reproduce the issue, and there seem to be multiple
> problems. Specifically we have an issue when upgrading a defau
My bad: s3cmd errors were unrelated to Jewel upgrade and Yehuda's script:
It required an upgrade from s3cmd from 1.5 to 1.6 - sorry for the noise.
Will try to replicate the upgrade.
On Tue, Apr 26, 2016 at 9:27 PM, Richard Chan
wrote:
> Also s3cmd is unable to create new buckets:
>
> # s3cmd
Summary of Yehuda's script on Hammer -> Jewel upgrade:
1. It works: users, buckets, objects now accessible: the zonegroup and zone
have been set to "default" ( previouslly zone = "" and region = "")
2. s3cmd needed to be upgraded to 1.6 to work
Thanks.
On Tue, Apr 26, 2016 at 8:06 AM, Yehuda
hi,
my pools ar named a bit fifferent fomr the dafault ones:
.dev-qa.rgw.gc
.rgw.control
.dev-qa.users.uid
.dev-qa.users.swift
.dev.rgw.root
.dev-qa.usage
.dev-qa.log
.dev-qa.rgw.buckets
.dev-qa.rgw.buckets.index
.dev-qa.rgw.root
.dev-qa.users.email
.dev-qa.intent-log
.dev-qa.rgw.buckets.extra
.d
I've upgraded our test cluster from 9.2.1 to 10.2.1 and I still had
these issues. As before the script did fix the issue and the cluster
is now working.
Is the correct fix in 10.2.1 or was it still expected to run the fix?
If it makes a difference I'm running trusty, the cluster was created
on ha
14 matches
Mail list logo
