[HDDS-3513] Add OzoneConfiguration to UGI when startup S3Gateway

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.5.0
• Fix Version/s: 1.0.0
• Component/s: S3
• Labels: pull-request-available pull-requests-available
• Assignee: Simon Su
• Reporter: Simon Su
• Created: 30/Apr/20 05:29
• Updated: 07/May/20 17:03
• Resolved: 07/May/20 04:47

Description

OzoneConfiguration missing load ozone-site.xml by default, this may cause some issues when setup a secure ozone cluster.

When we start a S3Gateway in secure mode (Kerberos), when start S3Gateway http server, it will use UserGroupInformation to check whether in security mode, which will load Configuration to check whether "hadoop.security.authentication" set to "KERBEROS". but unfortunately, default configuration will only load "core-site.xml, core-default.xml, hdfs-site.xml, hdfs-default.xml ozone-default.xml" and missing ozone-site.xml,  it means we have to configure "hadoop.security.authentication" in one of default 5 config files if we want to start a secure S3Gateway.

It's better to add ozone-site.xml into OzoneConfiguration by default, so we don't need to make one same configuration in different part.

Issue Links

• links to: GitHub Pull Request #897