I am running into this issue as well with a cephadm reef deploy, are there any
updates?
___
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
SOLVED!
OK, there was some last-minute flailing around so I can't quite report
a cookbook recipe, but it goes something like this:
1. ceph config set client.mousetech rgw_admin_entry admin
Note: the standard example is for client.rgw, but I named my RGW
"mousetech" to make it distinguishable fr
you're right that many docs still mention ceph.conf, after the mimic
release added a centralized config database to ceph-mon. you can read
about the mon-based 'ceph config' commands in
https://docs.ceph.com/en/reef/rados/configuration/ceph-conf/#commands
to modify rgw_admin_entry for all radosgw i
Thanks, Casey!
I'm not really certain where to set this option. While Ceph is very
well-behaved once you know what to do, the nature of Internet-based
documentation (and occasionally incompletely-updated manuals) is that
stale information is often given equal weight to the obsolete
information. It
hey Tim,
your changes to rgw_admin_entry probably aren't taking effect on the
running radosgws. you'd need to restart them in order to set up the
new route
there also seems to be some confusion about the need for a bucket
named 'default'. radosgw just routes requests with paths starting with
'/{r
Thank you, Ondřej!
Yes, I set the admin entry set to "default". It's just the latest
result of failed attempts ("admin" didn't work for me either). I did
say there were some horrors in there!
If I got your sample URL pattern right, the results of a GET on
"http://x.y.z/default"; return 404, NoSuc
Hello Tim,
I was also struggling with this when I was configuring the object gateway for
the first time.
There is a few things that you should check to make sure the dashboard would
work.
1. You need to have the admin api enabled on all rgws with the rgw_enable_apis
option. (As far as I know
