[ 
https://issues.apache.org/jira/browse/HADOOP-14334?focusedWorklogId=705829&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-705829
 ]

ASF GitHub Bot logged work on HADOOP-14334:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 09/Jan/22 18:02
            Start Date: 09/Jan/22 18:02
    Worklog Time Spent: 10m 
      Work Description: steveloughran merged pull request #3870:
URL: https://github.com/apache/hadoop/pull/3870


   


-- 
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]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 705829)
    Time Spent: 1h 10m  (was: 1h)

> S3 SSEC  tests to downgrade when running against a mandatory encryption 
> object store
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-14334
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14334
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3, test
>    Affects Versions: 2.9.0
>            Reporter: Steve Loughran
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> If you run the S3A tests against a bucket with mandatory encryption, you need 
> to set the encryption in auth keys. This breaks the SSEC tests because the 
> encryption.key property being set breaks them. 
> That can be fixed (unset it), but they also need to handle failure from the 
> wrong encryption mech being used. Proposed: catch and downgrade to skipped.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to