accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Havanki (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-2211) Security randomwalk fails "User doesn't exist and they SHOULD"
Date Fri, 17 Jan 2014 04:04:19 GMT


Bill Havanki commented on ACCUMULO-2211:

The commit just now is a one-liner. I'm confident enough in it that I'm throwing caution to
the wind and just committing it without review. I know, what's gotten into me.

I observes the additional delay in effect in a run of the Security test. I also identified
a traversal of the same nodes that produced the error condition, which this time succeeded.

> Security randomwalk fails "User doesn't exist and they SHOULD"
> --------------------------------------------------------------
>                 Key: ACCUMULO-2211
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Bill Havanki
>            Assignee: Bill Havanki
>            Priority: Minor
>              Labels: randomwalk, test
>             Fix For: 1.4.5, 1.5.1, 1.6.0
> The CreateUser node in the Security randomwalk test can create the "table" user even
in the face of an expected PERMISSION_DENIED error. When that happens, and the next node happens
to want to change the new table user's password, you can get:
> {noformat}
> org.apache.accumulo.core.client.AccumuloException: User table_server_domain_com_29780_1389915181300
doesn't exist and they SHOULD.
> {noformat}
> This happens because there is no delay between the user creation and the password change,
as there are for other user creations, added in ACCUMULO-1123.

This message was sent by Atlassian JIRA

View raw message