aws s3 sync doesn't allow to skip unreadable files

[ovcharenko]

Issue Type:

BugReport

AWS-CLI Version:

1.3.6

Environment:

N/A

Summary:

aws s3 sync fails immediately when it found any read error:

1. Missing symlink
2. Wrong permission
3. FuSE mounted folder

Steps To Reproduce:

Try to sync home folders as root on Ubuntu. They all may contain ~/.gvfs mounted by gvfs-fuse-daemon

Expected Results:

Files will be skipped and warning displayed.

Actual Results:

Whole sync stopped.

[jamesls]

Based on previous issues, I think supporting this functionality would be good, but we can't change the default behavior. There was talk in a previous discussion (#425) about making this opt in (i.e. --ignore-io-errors or maybe --ignore-read-errors) where we would log the error, continue transferring files, but exit with a non-zero rc to indicate that not all files transferred.

[jamesls]

This is now fixed via #881