zookeeper-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-2712) MiniKdc test case intermittently failing due to principal not found in Kerberos database
Date Sat, 18 Mar 2017 21:57:42 GMT

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

ASF GitHub Bot commented on ZOOKEEPER-2712:
-------------------------------------------

Github user hanm commented on a diff in the pull request:

    https://github.com/apache/zookeeper/pull/200#discussion_r106792158
  
    --- Diff: src/java/test/org/apache/zookeeper/server/quorum/auth/QuorumAuthUpgradeTest.java
---
    @@ -83,7 +83,7 @@ public void testNullAuthLearnerServer() throws Exception {
             Map<String, String> authConfigs = new HashMap<String, String>();
             authConfigs.put(QuorumAuth.QUORUM_SASL_AUTH_ENABLED, "false");
     
    -        String connectStr = startQuorum(2, authConfigs, 0);
    +        String connectStr = startQuorum(2, authConfigs, 0, false);
    --- End diff --
    
    I am curious why we don't need a delay here - is it because the ApacheDS is not used in
this test case?


> 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
>            Priority: Critical
>             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