shunki-fujita opened a new pull request, #10817:
URL: https://github.com/apache/gravitino/pull/10817

   PR #10681 switched the gravitino and iceberg-rest-server Docker images to 
run as non-root (USER 1000) but did not create a corresponding /etc/passwd 
entry. This causes Hadoop's UserGroupInformation to fail with a 
NullPointerException in UnixLoginModule.login() when it cannot resolve the UID 
to a username.
   
   In the iceberg-rest-server, this manifests as HTTP 500 errors after the 
IcebergCatalogWrapper cache is evicted, because the wrapper re-creation calls 
FileSystemUtils.createConfiguration() which triggers UGI initialization. The 
first request after server startup succeeds because UGI's static state is not 
yet initialized.
   
   Add useradd to both Dockerfiles so that UID 1000 is registered in 
/etc/passwd, allowing UnixLoginModule to resolve the username.
   
   <!--
   1. Title: [#<issue>] <type>(<scope>): <subject>
      Examples:
        - "[#123] feat(operator): Support xxx"
        - "[#233] fix: Check null before access result in xxx"
        - "[MINOR] refactor: Fix typo in variable name"
        - "[MINOR] docs: Fix typo in README"
        - "[#255] test: Fix flaky test NameOfTheTest"
      Reference: https://www.conventionalcommits.org/en/v1.0.0/
   2. If the PR is unfinished, please mark this PR as draft.
   -->
   
   ### What changes were proposed in this pull request?
   
   (Please outline the changes and how this PR fixes the issue.)
   
   ### Why are the changes needed?
   
   (Please clarify why the changes are needed. For instance,
     1. If you propose a new API, clarify the use case for a new API.
     2. If you fix a bug, describe the bug.)
   
   Fix: #(issue)
   
   ### Does this PR introduce _any_ user-facing change?
   
   (Please list the user-facing changes introduced by your change, including
     1. Change in user-facing APIs.
     2. Addition or removal of property keys.)
   
   ### How was this patch tested?
   
   (Please test your changes, and provide instructions on how to test it:
     1. If you add a feature or fix a bug, add a test to cover your changes.
     2. If you fix a flaky test, repeat it for many times to prove it works.)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to