Bucket information exsists in two places, an object in moss.buckets bucket and an entry in bucket list in user record.
Some subtle situation can happens if the combination of these becomes inconsistent.
Typical symptom is that
- List buckets shows a bucket but
- user can not access the bucket (list objects or get/put objects in the bucket)
- also can not delete or create the bucket.
Users can not bring thist this situation back to normal. Current workaround is to set disable_local_bucket_check=true in app.config, then create the bucket and delete it.
This can be solved by removing the entry from bucket list in user record when
- the request is DELETE for bucket resource and
- the bucket does not exist in
moss.buckets bucket ("not exist" includes delete marker).
Currently, ACL/Policy check fails by notfound / no_such_bucket.