ctubbsii opened a new issue, #3075:
URL: https://github.com/apache/accumulo/issues/3075
**Test name(s)**
- AuthenticationTokenSecretManagerTest.testVerifyPassword
**Describe the failure observed**
There seems to be some small probability that the
AuthenticationTokenSecretManager will generate the same random password. I've
seen the following error a few times, but it's hard to reproduce. Since it's
calling into Hadoop code to generate things, this could depend on specific
Hadoop versions.
```
[ERROR] Tests run: 10, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
11.485 s <<< FAILURE! - in
org.apache.accumulo.server.security.delegation.AuthenticationTokenSecretManagerTest
[ERROR]
org.apache.accumulo.server.security.delegation.AuthenticationTokenSecretManagerTest.testVerifyPassword
Time elapsed: 0.003 s <<< FAILURE!
org.opentest4j.AssertionFailedError: Different tokens for the same user
shouldn't have the same password ==> expected: <false> but was: <true>
at
org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
at
org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)
at org.junit.jupiter.api.AssertFalse.failNotFalse(AssertFalse.java:63)
at org.junit.jupiter.api.AssertFalse.assertFalse(AssertFalse.java:36)
at org.junit.jupiter.api.Assertions.assertFalse(Assertions.java:236)
at
org.apache.accumulo.server.security.delegation.AuthenticationTokenSecretManagerTest.testVerifyPassword(AuthenticationTokenSecretManagerTest.java:222)
```
**Additional context**
If I remember correctly, this code is part of the delegation token
management stuff that is used with Kerberos-enabled clusters so that MapReduce
and other similar tasks don't need a keytab for each individual job task. Most
recently, I saw this on 3.0.0-SNAPSHOT in the main branch, but I've previously
seen it in development on earlier branches as well.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
