Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D44710282 for ; Fri, 17 Jan 2014 04:04:24 +0000 (UTC) Received: (qmail 61817 invoked by uid 500); 17 Jan 2014 04:04:21 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 61693 invoked by uid 500); 17 Jan 2014 04:04:20 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 61672 invoked by uid 99); 17 Jan 2014 04:04:20 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Jan 2014 04:04:20 +0000 Date: Fri, 17 Jan 2014 04:04:19 +0000 (UTC) From: "Bill Havanki (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (ACCUMULO-2211) Security randomwalk fails "User doesn't exist and they SHOULD" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13874407#comment-13874407 ] Bill Havanki edited comment on ACCUMULO-2211 at 1/17/14 4:03 AM: ----------------------------------------------------------------- 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 observed 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. was (Author: bhavanki): 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: https://issues.apache.org/jira/browse/ACCUMULO-2211 > 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 (v6.1.5#6160)