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

sync and cp does not work as expected #4268

Closed
S0uLHun43r opened this issue Jun 26, 2019 · 2 comments
Closed

sync and cp does not work as expected #4268

S0uLHun43r opened this issue Jun 26, 2019 · 2 comments
Assignees
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. guidance Question that needs advice or information. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. third-party This issue is related to third-party libraries or applications.

Comments

@S0uLHun43r
Copy link

The same problem here, awscli==1.16.186
aws s3 cp and aws s3 sync happen same .

I have 1217 files.but sync and cp all give 1000 files.

but when i use s3cmd,it works . @JordonPhillips please open this issue
image

@justnance justnance self-assigned this Jul 4, 2019
@justnance justnance added closing-soon This issue will automatically close in 4 days unless further comments are made. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. labels Jul 4, 2019
@justnance
Copy link

justnance commented Jul 4, 2019

@S0uLHun43r - Thanks for reporting this issue. It appears this is related to issue #3087. I not able to reproduce the same problem after testing with both the s3 cp and s3 sync command, the latest version of the CLI, and with a bucket with 1200 items of various file types. With the screen shot provided, I see there is a 3rd party endpoint in use:

aws s3 --endpoint=http://ceph.whlocal.com:8080 sync s3://ums-tmp/umpic/JPG/...
aws s3 --endpoint=http://ceph.whlocal.com:8080 ls s3://ums-tmp/umpic/JPG/...

It appears the return of "1000 files" instead of all 1217 is because the 3rd party endpoint is not working with the CLI pagination where it is not returning the next page token. If you add the --debug option on the end of the command it may show if there is an error around the continuation-token. It is possible the next page token may not be support by Ceph. As such, this behavior is not controlled by the CLI.

@justnance justnance added third-party This issue is related to third-party libraries or applications. guidance Question that needs advice or information. labels Jul 10, 2019
@no-response
Copy link

no-response bot commented Jul 11, 2019

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closing-soon This issue will automatically close in 4 days unless further comments are made. guidance Question that needs advice or information. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. third-party This issue is related to third-party libraries or applications.
Projects
None yet
Development

No branches or pull requests

2 participants