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 DC3FB200CA8 for ; Thu, 15 Jun 2017 15:22:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DAC38160BED; Thu, 15 Jun 2017 13:22:05 +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 2C5A6160BC4 for ; Thu, 15 Jun 2017 15:22:05 +0200 (CEST) Received: (qmail 1307 invoked by uid 500); 15 Jun 2017 13:22:04 -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 1296 invoked by uid 99); 15 Jun 2017 13:22:04 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jun 2017 13:22:04 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D8FAD180313 for ; Thu, 15 Jun 2017 13:22:03 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id ZsY77-t-BJbG for ; Thu, 15 Jun 2017 13:22:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 709BC5F6BF for ; Thu, 15 Jun 2017 13:22:01 +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 E754CE0A2F for ; Thu, 15 Jun 2017 13:22:00 +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 32B5421D8F for ; Thu, 15 Jun 2017 13:22:00 +0000 (UTC) Date: Thu, 15 Jun 2017 13:22:00 +0000 (UTC) From: "Steve Loughran (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HADOOP-14528) s3a encryption tests fail when dest bucket has fs.s3a.server-side-encryption.key set MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 15 Jun 2017 13:22:06 -0000 [ https://issues.apache.org/jira/browse/HADOOP-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16050464#comment-16050464 ] Steve Loughran commented on HADOOP-14528: ----------------------------------------- Stack in SSE-C test. AWS s3 is handed the key ref from {{fs.s3a.server-side-encryption.key}}, assuming it's a base-64 key and failing at parse time. This is something to consider covering in troubleshooting docs. {code} Running org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSECBlockOutputStream Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.156 sec <<< FAILURE! - in org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSECBlockOutputStream testEncryptionOverRename(org.apache.hadoop.fs.s3a.ITestS3AEncryptionSSECBlockOutputStream) Time elapsed: 0.042 sec <<< ERROR! java.lang.IllegalArgumentException: Input is expected to be encoded in multiple of 4 bytes but found: 75 at com.amazonaws.util.Base64Codec.decode(Base64Codec.java:198) at com.amazonaws.util.Base64.decode(Base64.java:89) at com.amazonaws.services.s3.AmazonS3Client.populateSSE_C(AmazonS3Client.java:3840) at com.amazonaws.services.s3.AmazonS3Client.getObjectMetadata(AmazonS3Client.java:1247) at org.apache.hadoop.fs.s3a.S3AFileSystem.getObjectMetadata(S3AFileSystem.java:941) at org.apache.hadoop.fs.s3a.S3AFileSystem.getFileStatus(S3AFileSystem.java:1611) at org.apache.hadoop.fs.s3a.S3AFileSystem.innerMkdirs(S3AFileSystem.java:1562) at org.apache.hadoop.fs.s3a.S3AFileSystem.mkdirs(S3AFileSystem.java:1539) at org.apache.hadoop.fs.FileSystem.mkdirs(FileSystem.java:2230) at org.apache.hadoop.fs.contract.AbstractFSContractTestBase.mkdirs(AbstractFSContractTestBase.java:338) at org.apache.hadoop.fs.contract.AbstractFSContractTestBase.setup(AbstractFSContractTestBase.java:193) at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55) at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:74) {code} > s3a encryption tests fail when dest bucket has fs.s3a.server-side-encryption.key set > ------------------------------------------------------------------------------------- > > Key: HADOOP-14528 > URL: https://issues.apache.org/jira/browse/HADOOP-14528 > Project: Hadoop Common > Issue Type: Sub-task > Components: fs/s3, test > Environment: test bucket with SSE-KMS required > Reporter: Steve Loughran > > When testing against a bucket set up to require SSE-KMS, and with the bucket settings enabling this & providing the key in {{ fs.s3a.server-side-encryption.key}}, some of the encryption tests fail. > Not sure whether this can/should be fixed, except by saying "disable encryption tests here" that is: don't try to be clever about detecting this conditions and skipping the tests automatically -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org