Major Description
In MiniSentry, the JAVA_TOOL_OPTIONS environment variable is set into the environment upon every start of Sentry process by the MiniSentry::Start() method. In most cases it's being picked up, but sometimes that fails in the TestSentryClientMetrics.Basic test scenario. When that happens, the tests fails. An example of failure log is below:
[----------] 1 test from TestSentryClientMetrics
[ RUN ] TestSentryClientMetrics.Basic
Picked up JAVA_TOOL_OPTIONS:
16:45:18.723 [SENTRY - WARN - main] (Log4JLogger.java:96) Metadata has jdbc-type of null yet this is not valid. Ignored
16:45:20.587 [SENTRY - WARN - main] (Log4JLogger.java:96) Metadata has jdbc-type of null yet this is not valid. Ignored
16:45:22.701 [SENTRY - WARN - sentry-service] (Log4JLogger.java:96) Metadata has jdbc-type of null yet this is not valid. Ignored
Sentry service is ready to serve client requests
W0409 16:45:23.483585 28712 client.h:346] Failed to connect to Sentry (127.23.212.1:35614): Not authorized: failed to open Sentry connection: Configuration file does not specify default realm
/data/somelongdirectorytoavoidrpathissues/src/kudu/src/kudu/master/sentry_authz_provider-test.cc:686: Failure
Expected: 1
To be equal to: GetTasksSuccessful()
Which is: 0
I0409 16:45:23.520182 24400 test_util.cc:135] -----------------------------------------------
I0409 16:45:23.520295 24400 test_util.cc:136] Had fatal failures, leaving test files at /data/somelongdirectorytoavoidrpathissues/src/kudutest/sentry_authz_provider-test.1.TestSentryClientMetrics.Basic.1554853465542407-24400
[ FAILED ] TestSentryClientMetrics.Basic (11490 ms)
[----------] 1 test from TestSentryClientMetrics (11490 ms total)