zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rakesh R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database
Date Fri, 17 Mar 2017 17:06:41 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-2712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930308#comment-15930308
] 

Rakesh R commented on ZOOKEEPER-2712:
-------------------------------------

Thanks [~hanm] for the offline discussion about the static tool warnings.
{code}
-1 javadoc. The javadoc tool appears to have generated 1 warning messages.
{code}
Jira has broken links, am adding [patchJavadocWarnings.txt|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/patchprocess/patchJavadocWarnings.txt]
link.

{code}
-1 findbugs. The patch appears to introduce 97 new Findbugs (version 3.0.1) warnings.
{code}
Jira has broken links, am adding [newPatchFindbugsWarnings.html|https://builds.apache.org/job/PreCommit-ZOOKEEPER-github-pr-build/444/artifact/build/test/findbugs/newPatchFindbugsWarnings.html]
link.

It looks like entire project items are showing. The proposed fix is majorily touching test
code apart from one source code QuorumPeer.java. So, anything required here?




> 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.10
>
>         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)

Mime
View raw message