Ceph » rgw

currently when proper policy is not set on the log bucket, bucket logging operation fail with 403. giving the impression that there is access issue with the source bucket.
note that this may happen in the case that proper policy existed for setting the bucket logging configuration on the source, but not when loggign is attempted due to an operation on the source.
e.g. policy was removed or modified from log bucket after the fact or the "Resource" field in the policy was not set correctly

this will be even more confusing for the client as the failed operation will be unrelated to bucket logging at all.
we should make sure that in such cases, on top of the 403 code we should add proper information in the error section of the response body, indicating that the access issue was related to the log bucket.