Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

aws s3 recursive copy errors out #8662

Closed
manivmtc opened this issue May 2, 2024 · 2 comments
Closed

aws s3 recursive copy errors out #8662

manivmtc opened this issue May 2, 2024 · 2 comments
Assignees
Labels
bug This issue is a bug. p2 This is a standard priority issue s3

Comments

@manivmtc
Copy link

manivmtc commented May 2, 2024

Describe the bug

The command
aws s3 cp local_folder s3://some-bucket/ --recursive
failed with the following message:
An error occurred (RequestTimeTooSkewed) when calling the CreateMultipartUpload operation: The difference between the request time and the current time is too large.

Expected Behavior

The copy should succeed or the error message should provide ways to mitigate or solve the issue

Current Behavior

An error occurred (RequestTimeTooSkewed) when calling the CreateMultipartUpload operation: The difference between the request time and the current time is too large.

Reproduction Steps

This could be reproduced perhaps by messing a bit with the ntpdate program

Possible Solution

  1. Either the clockskew should be true by default as several users have suggested previously.
    OR
  2. There should be a way to set the correctClockSkew property as documented in javascript sdk

Additional Information/Context

No response

CLI version used

ws-cli/2.15.43 Python/3.11.8 Linux/5.15.0-88-generic exe/x86_64.ubuntu.20 prompt/off

Environment details (OS name and version, etc.)

Ubuntu 20.04.4 LTS Codename:focal

@manivmtc manivmtc added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels May 2, 2024
@RyanFitzSimmonsAK RyanFitzSimmonsAK self-assigned this May 3, 2024
@RyanFitzSimmonsAK RyanFitzSimmonsAK added investigating This issue is being investigated and/or work is in progress to resolve the issue. s3 p2 This is a standard priority issue and removed needs-triage This issue or PR still needs to be triaged. labels May 3, 2024
@RyanFitzSimmonsAK
Copy link
Contributor

Hi @manivmtc, thanks for reaching out. We have an existing issue tracking this feature request (boto/boto3#1252), which I'll bring up with the team. In the meantime, I'd recommend +1-ing that issue, and trying to sync your system clock if you haven't done so already. I'll leave an update in the tracking issue when I know more.

@RyanFitzSimmonsAK RyanFitzSimmonsAK closed this as not planned Won't fix, can't repro, duplicate, stale May 14, 2024
@RyanFitzSimmonsAK RyanFitzSimmonsAK removed the investigating This issue is being investigated and/or work is in progress to resolve the issue. label May 14, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue is a bug. p2 This is a standard priority issue s3
Projects
None yet
Development

No branches or pull requests

2 participants