Philip Zeyliger created IMPALA-7390:
---------------------------------------
Summary: rpc-mgr-kerberized-test fails inside of test-with-docker
for hostname resolution reasons
Key: IMPALA-7390
URL: https://issues.apache.org/jira/browse/IMPALA-7390
Project: IMPALA
Issue Type: Task
Reporter: Philip Zeyliger
When running inside of test-with-docker, the test fails like so:
{code}
2018-08-02 15:11:38.846042 [==========] Running 1 test from 1 test case.
2018-08-02 15:11:38.846073 [----------] Global test environment set-up.
2018-08-02 15:11:38.846114 [----------] 1 test from
KerberosOnAndOff/RpcMgrKerberizedTest
2018-08-02 15:11:38.846159 [ RUN ]
KerberosOnAndOff/RpcMgrKerberizedTest.MultipleServicesTls/0
2018-08-02 15:11:38.846284 Aug 02 22:11:38 i-20180802-132959
krb5kdc[13121](info): AS_REQ (2 etypes {17 16}) 127.0.0.1: ISSUE: authtime
1533247898, etypes {rep=17 tkt=17 ses=17},
impala-test/i-20180802-132...@krbtest.com for krbtgt/krbtest....@krbtest.com
2018-08-02 15:11:38.846417 Aug 02 22:11:38 i-20180802-132959
krb5kdc[13121](info): TGS_REQ (2 etypes {17 16}) 127.0.0.1: LOOKING_UP_SERVER:
authtime 0, impala-test/i-20180802-132...@krbtest.com for
impala-test/localh...@krbtest.com, Server not found in Kerberos database
2018-08-02 15:11:38.846555 Aug 02 22:11:38 i-20180802-132959
krb5kdc[13121](info): TGS_REQ (2 etypes {17 16}) 127.0.0.1: LOOKING_UP_SERVER:
authtime 0, impala-test/i-20180802-132...@krbtest.com for
impala-test/localh...@krbtest.com, Server not found in Kerberos database
2018-08-02 15:11:38.846599
/home/impdev/Impala/be/src/rpc/rpc-mgr-kerberized-test.cc:72: Failure
2018-08-02 15:11:38.846619 Value of: status_.ok()
2018-08-02 15:11:38.846635 Actual: false
2018-08-02 15:11:38.846651 Expected: true
2018-08-02 15:11:38.846763 Error: unable to execute ScanMem() RPC.: Not
authorized: Client connection negotiation failed: client connection to
127.0.0.1:53900: Server impala-test/localh...@krbtest.com not found in Kerberos
database
{code}
The issue is that in this context the "hostname" is roughly mapping to
127.0.0.1 but then maps back to localhost.
The workaround is pretty straight-forward; patch forthcoming.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
