You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues-all@impala.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2018/08/08 07:27:01 UTC
[jira] [Commented] (IMPALA-7390) rpc-mgr-kerberized-test fails
inside of test-with-docker for hostname resolution reasons
[ https://issues.apache.org/jira/browse/IMPALA-7390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16572803#comment-16572803 ]
ASF subversion and git services commented on IMPALA-7390:
---------------------------------------------------------
Commit 2d6a459c76edbe619543fd50d68be72b79a63bc5 in impala's branch refs/heads/master from [~philip]
[ https://git-wip-us.apache.org/repos/asf?p=impala.git;h=2d6a459 ]
IMPALA-7390: Configure /etc/hosts to avoid rpc-mgr-kerberized-test issues.
In the test-with-docker context, rpc-mgr-kerberized-test was failing,
ultimately due to the fact that the hostname was resolving to 127.0.0.1
and then back to 'localhost'.
This commit applies a workaround of adding "127.0.0.1 $(hostnahostname)"
to /etc/hosts, which allows the test to pass, and is what's done in
bootstrap_system.sh. In the Docker context, /etc/hosts needs to be
updated on every container start, because Docker tries to provide an
/etc/hosts for you. Previously, we were doing a different customization
(adding "hostname" to the existing "127.0.0.1" line), which wasn't good
enough for rpc-mgr-kerberized-test.
The original workaround, which is in "boostrap_system.sh" is still
in place, but I've added more documentation about reproduction there.
I've also filed HDFS-13797 to track the HDFS issue.
Change-Id: I91003cbc86177feb7f99563f61297f7da7fabab4
Reviewed-on: http://gerrit.cloudera.org:8080/11113
Reviewed-by: Impala Public Jenkins <im...@cloudera.com>
Tested-by: Impala Public Jenkins <im...@cloudera.com>
> 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
> Priority: Major
>
> 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-132959@KRBTEST.COM for krbtgt/KRBTEST.COM@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-132959@KRBTEST.COM for impala-test/localhost@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-132959@KRBTEST.COM for impala-test/localhost@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/localhost@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)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org