You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@zookeeper.apache.org by "Rakesh R (JIRA)" <ji...@apache.org> on 2017/03/08 15:06:38 UTC
[jira] [Updated] (ZOOKEEPER-2712) MiniKdc test case intermittently
failing due to principal not found in Kerberos database
[ https://issues.apache.org/jira/browse/ZOOKEEPER-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rakesh R updated ZOOKEEPER-2712:
--------------------------------
Attachment: TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
I'm attaching the failure test case log.
> MiniKdc test case intermittently failing due to principal not found in Kerberos database
> ----------------------------------------------------------------------------------------
>
> Key: ZOOKEEPER-2712
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-2712
> Project: ZooKeeper
> Issue Type: Bug
> Components: tests
> Reporter: Rakesh R
> Assignee: Rakesh R
> Fix For: 3.4.11
>
> Attachments: TEST-org.apache.zookeeper.server.quorum.auth.QuorumKerberosAuthTest.txt
>
>
> MiniKdc test cases are intermittently failing due to not finding the principal. Below is the failure stacktrace.
> {code}
> 2017-03-08 13:21:10,843 [myid:] - ERROR [NioProcessor-1:AuthenticationService@187] - Error while searching for client learner@EXAMPLE.COM : Client not found in Kerberos database
> 2017-03-08 13:21:10,843 [myid:] - WARN [NioProcessor-2:KerberosProtocolHandler@241] - Server not found in Kerberos database (7)
> 2017-03-08 13:21:10,845 [myid:] - WARN [NioProcessor-2:KerberosProtocolHandler@242] - Server not found in Kerberos database (7)
> 2017-03-08 13:21:10,844 [myid:] - WARN [NioProcessor-1:KerberosProtocolHandler@241] - Client not found in Kerberos database (6)
> 2017-03-08 13:21:10,845 [myid:] - WARN [NioProcessor-1:KerberosProtocolHandler@242] - Client not found in Kerberos database (6)
> {code}
> Will attach the detailed log to jira.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)