Open nickbrennan1 opened 2 months ago
Hmm, this could be an interesting, can you please describe the enable dashboard and create user/bucket
step. ? Also, Can you try achieving the same (user/bucket) creation using the radosgw-admin
cli ?
We don't really test for setting up policies for buckets, it would be awesome if you could contribute a CI test for it. Public Matrix chat room
Thanks for the suggestion, I'll retry with the CLI. Have added the notes on enabling dashboard etc in a gist above
I've been able to create a user and add capabilities with radosgw-admin
. However, there appears to be no option to create bucket, either in the radosgw-admin
help page or the main guide:
bucket list list buckets (specify --allow-unordered for faster, unsorted listing)
bucket limit check show bucket sharding stats
bucket link link bucket to specified user
bucket unlink unlink bucket from specified user
bucket stats returns bucket statistics
bucket rm remove bucket
bucket check check bucket index
bucket chown link bucket to specified user and update its object ACLs
bucket reshard reshard bucket
bucket rewrite rewrite all objects in the specified bucket
bucket sync checkpoint poll a bucket's sync status until it catches up to its remote
bucket sync disable disable bucket sync
bucket sync enable enable bucket sync
bucket radoslist list rados objects backing bucket's objects
....and if I use s3cmd
I get the same behaviour as the problem statement:
root@ceph:~/ceph# s3cmd mb s3://clitest
ERROR: S3 error: 405 (MethodNotAllowed)
radosgw-admin
will list available buckets and their content. I can also use s3cmd PUT
to copy up objects, so some of the interface works and the creds in .s3cfg
are correct.
Issue report
What version of MicroCeph are you using ?
Name Version Rev Tracking Publisher Notes microceph 0+git.287ee68 807 quincy/edge canonical✓ held
What are the steps to reproduce this issue ?
What happens (observed behaviour) ?
At this point any calls to the RGW endpoint (default port 80) appear to fail, ie to set a new policy on the bucket:
And from the RGW logs:
All calls will fail except an
INFO
on the bucket, ie:Gist with detail here
What were you expecting to happen ?
Expectation is that standard API calls will work
Additional comments.
Possibly the problems are occurring because no privileges are set on hte bucket yet, but without the ability to apply a policy there appears to be no way round this