[HDDS-6574] Set owner of buckets created via S3 Gateway to actual user rather than `s3g`; print LinkBucket owner field on the client

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.3.0
• Fix Version/s: 1.3.0
• Component/s: Ozone Client
• Labels: pull-request-available
• Target Version/s: 1.3.0
• Assignee: Siyao Meng
• Reporter: Siyao Meng
• Created: 12/Apr/22 16:22
• Updated: 21/Apr/22 07:09
• Resolved: 19/Apr/22 08:08

Description

Currently if a bucket is created using S3 API via S3 Gateway, the bucket owner is always set to "s3g" (whoever S3 Gateway authenticated itself as to the Ozone Manager).

Current behavior when a bucket is created using S3 API via S3 Gateway

$ ozone sh bucket list /tenant1
[ {
  "metadata" : { },
  "volumeName" : "s3v",
  "name" : "bucket1",
  "storageType" : "DISK",
  "versioning" : false,
  "usedBytes" : 0,
  "usedNamespace" : 0,
  "creationTime" : "2022-04-07T14:51:49.053Z",
  "modificationTime" : "2022-04-07T14:51:49.053Z",
  "quotaInBytes" : -1,
  "quotaInNamespace" : -1,
  "bucketLayout" : "OBJECT_STORE",
  "owner" : "s3g",  <---
  "link" : false
} ]

This bucket owner field should be set to the user behind the accessId (short name) as this should be the intended behavior.

Expected behavior

$ ozone sh bucket list /tenant1
[ {
...
  "bucketLayout" : "OBJECT_STORE",
  "owner" : "hive",  <---
  "link" : false
} ]

See the PR description for more details.

Issue Links

• is a parent of: HDDS-6625 [Multi-Tenant] Follow-up: Set owner of buckets created via S3 Gateway to actual user
• is related to: HDDS-5903 Add support for Bucket Owner ACLs
• links to: GitHub Pull Request #3298