Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0BB7F200C23 for ; Wed, 22 Feb 2017 21:03:52 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 0A4BE160B62; Wed, 22 Feb 2017 20:03:52 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 4EA6F160B49 for ; Wed, 22 Feb 2017 21:03:51 +0100 (CET) Received: (qmail 63549 invoked by uid 500); 22 Feb 2017 20:03:50 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 63538 invoked by uid 99); 22 Feb 2017 20:03:50 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Feb 2017 20:03:50 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id DBE09C193A for ; Wed, 22 Feb 2017 20:03:49 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.199 X-Spam-Level: X-Spam-Status: No, score=-1.199 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id cmlLFCRzCVBj for ; Wed, 22 Feb 2017 20:03:48 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 57BDB5F30F for ; Wed, 22 Feb 2017 20:03:48 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id DF2E0E0A6C for ; Wed, 22 Feb 2017 20:03:44 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5BEA724129 for ; Wed, 22 Feb 2017 20:03:44 +0000 (UTC) Date: Wed, 22 Feb 2017 20:03:44 +0000 (UTC) From: "Aaron Fabbri (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-14102) Relax error message assertion in S3A test ITestS3AEncryptionSSEC::testCreateFileAndReadWithDifferentEncryptionKey MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 22 Feb 2017 20:03:52 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879118#comment-15879118 ] Aaron Fabbri commented on HADOOP-14102: --------------------------------------- Thanks for taking the time to do this [~liuml07]. Looks good to me. > Relax error message assertion in S3A test ITestS3AEncryptionSSEC::testCreateFileAndReadWithDifferentEncryptionKey > ----------------------------------------------------------------------------------------------------------------- > > Key: HADOOP-14102 > URL: https://issues.apache.org/jira/browse/HADOOP-14102 > Project: Hadoop Common > Issue Type: Test > Components: fs/s3 > Reporter: Mingliang Liu > Assignee: Mingliang Liu > Priority: Minor > Attachments: HADOOP-14102.000.patch > > > [HADOOP-13075] added support for SSE-KMS and SSE-C in s3a filesystem, along with integration test {{ITestS3AEncryptionSSEC::testCreateFileAndReadWithDifferentEncryptionKey}}. For {{AccessDeniedException}} test case, it assumes the error message contains string _Forbidden (Service: Amazon S3; Status Code: 403;_, which is true in the current AWS java sdk and current S3AFileSystem code path. > When enabling S3Guard (see feature JIRA [HADOOP-13345]), the code path that fails in {{S3AFileSystem}} changes for that test. Specifically, the request w/o S3Guard was calling {{getFileStatus()}} and fails with access denied exception containing _Forbidden_ keyword; while the request w/ S3Guard is able to call {{getFileStatus()}} successfully and then fails later for read operations with access denied exception containing _Access Denied_ keyword. > AWS sdk does not provide the exactly same error message for different AccessDeniedExceptions. In the meantime, the AWS sdk may evolve (as we have been upgrading the sdk version recently in a timely manner) and the error message may be different in the future. This is to relax exception message assertion in test. > Thanks [~fabbri] for discussion. See [HADOOP-13345]. -- This message was sent by Atlassian JIRA (v6.3.15#6346) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org