[
https://issues.apache.org/jira/browse/CASSANDRA-12064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15344929#comment-15344929
]
Sam Tunnicliffe commented on CASSANDRA-12064:
---------------------------------------------
I think we need some additional logging in the dtest to diagnose this.
All we know is that the client was not able to connect when it supplied the bad
password, but that the exception was not {{AuthenticationFailed}}. The server
was operational at that point as the connection with the correct password had
already succeeded. There's nothing in the server logs to indicate what the
problem might be and I don't see any huge pauses in the GC log, so my only
suggestion is to have the dtest output which exception it hits & check if the
test fails again (though this particular test is very old and hasn't failed in
around forever).
> dtest failure in auth_test.TestAuth.login_test
> ----------------------------------------------
>
> Key: CASSANDRA-12064
> URL: https://issues.apache.org/jira/browse/CASSANDRA-12064
> Project: Cassandra
> Issue Type: Test
> Reporter: Sean McCarthy
> Assignee: DS Test Eng
> Labels: dtest
> Attachments: node1.log, node1_debug.log, node1_gc.log
>
>
> example failure:
> http://cassci.datastax.com/job/trunk_dtest/1284/testReport/auth_test/TestAuth/login_test
> Failed on CassCI build trunk_dtest #1284
> {code}
> Stacktrace
> File "/usr/lib/python2.7/unittest/case.py", line 329, in run
> testMethod()
> File "/home/automaton/cassandra-dtest/auth_test.py", line 82, in login_test
> assert isinstance(e.errors.values()[0], AuthenticationFailed)
> {code}
> Logs are attached.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
