Ceph » rgw

In Ceph 18.2.4, the X-RGW-Quota-Bucket-Objects header always contains the
quota value of the actual bucket, even if the quota is not enabled per-bucket, but
per-user.

Here's a bucket with a per-user quota:

$ radosgw-admin user info --uid $uid | jq .bucket_quota
{
  "enabled": true,
  "check_on_raw": false,
  "max_size": -1,
  "max_size_kb": 0,
  "max_objects": 10000000
}

$ radosgw-admin bucket stats --bucket $bucket | jq .bucket_quota
{
  "enabled": false,
  "check_on_raw": false,
  "max_size": -1,
  "max_size_kb": 0,
  "max_objects": -1
}

# Using a recent curl release (e.g. 8.7+)
$ curl $objects_url/$bucket --request HEAD --user $access_key:$secret_key --aws-sigv4 "aws:amz:us-east-1:s3" -v 2>&1 | grep bucket-object
< x-rgw-quota-bucket-objects: -1

Changing the bucket quota, even though it is not enabled, causes the header to be set ot the given quota:

radosgw-admin quota set --quota-scope=bucket --max-objects=100 --bucket $bucket

$ radosgw-admin bucket stats --bucket $bucket | jq .bucket_quota
{
  "enabled": false,
  "check_on_raw": false,
  "max_size": -1,
  "max_size_kb": 0,
  "max_objects": 100
}

$ curl $objects_url/$bucket --request HEAD --user $access_key:$secret_key --aws-sigv4 "aws:amz:us-east-1:s3" -v 2>&1 | grep bucket-object
< x-rgw-quota-bucket-objects: 100

Note that the per-bucket quota did not have to be enabled for the value to change.

I'm not sure how this is designed to work, but I naively expected these headers to reflect the quota that's actually applied.