[HADOOP-16420] S3A returns 400 "bad request" on a single path within an S3 bucket

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Cannot Reproduce
• Affects Version/s: 3.3.0
• Component/s: fs/s3
• Assignee: Unassigned
• Reporter: Steve Loughran
• Created: 10/Jul/19 18:42
• Updated: 10/Jul/19 18:51
• Resolved: 10/Jul/19 18:51

Description

Filing this as "who knows?"; surfaced during testing. Notable that the previous testing was playing with SSE-C, if that makes a difference: it could be that there's a marker entry encrypted with SSE-C that is now being rejected by a different run.

Somehow, with a set of credentials I can work with all paths in a directory, except read the dir marker /fork-0001/"; try that and a 400 bad request comes back. AWS console views the path as an empty dir.