AWS S3 Cloud Sync previously working now failing

[nbowman]

Hello, I've recently updated to Freenas 11.2

FreeBSD freenas.localdomain 11.2-STABLE FreeBSD 11.2-STABLE #0 r325575+3a9793238ff(freenas/11.2-stable): Thu Nov 15 13:51:02 EST 2018 root@nemesis.tn.ixsystems.com:/freenas-11.2-releng/freenas/_BE/objs/freenas-11.2-releng/freenas/_BE/os/sys/FreeNAS.amd64 amd64

I just noticed that my cloud sync task is now failing, which was previously working, prior to update. I also noticed there's a log file available for download from the GUI, so I took a peek and here's what I've found.

2018/11/27 10:44:42 ERROR : : error reading destination directory: RequestError: send request failed
caused by: Get https://s3.None.amazonaws.com/xxxxxxxx?delimiter=%2F&max-keys=1000&prefix=xxxxxxx%2F: dial tcp: lookup s3.None.amazonaws.com on 8.8.8.8:53: no such host
2018/11/27 10:44:42 INFO : S3 bucket xxxxxxxx path xxxxxxxx/: Waiting for checks to finish
2018/11/27 10:44:42 INFO : S3 bucket xxxxxxxx path xxxxxxxx/: Waiting for transfers to finish
2018/11/27 10:44:42 ERROR : S3 bucket xxxxxxxx path xxxxxxxx/: not deleting files as there were IO errors
2018/11/27 10:44:42 ERROR : S3 bucket xxxxxxxx path xxxxxxxx/: not deleting directories as there were IO errors
2018/11/27 10:44:42 ERROR : Attempt 1/3 failed with 1 errors and: not deleting files as there were IO errors

I believe this has something to do with the hostname DNS is trying to resolve (s3.None.amazonaws.com). Is this a bug? I've tried to workaround this by specifying valid Endpoint URLs (s3.amazonaws.com) and here are the results:

2018/11/27 11:00:52 ERROR : : error reading destination directory: AuthorizationHeaderMalformed: The authorization header is malformed; the region 'None' is wrong; expecting 'us-east-1'


Any one have any insight or suggestions? I tried to see if any one has posted about this previously, but I wasn't able to find any thing. I'm willing to give suggestions a try and will provide a quick update on the results. Thanks!

 

[dlavigne]

Thanks for reporting the bug, Nick.

Notes that the bug is https://redmine.ixsystems.com/issues/60135 but will be hidden from others until the dev has a chance to review his debug.

 

[GBillR]

For those who stumble across this post (as I did) while trying to figure out why your Amazon S3 Cloud Sync tasks are failing:
The short answer to fix this is to simply open the task for edit and then save the task again (with no changes).

 

[TooMuchData]

Yup. Edit, save, run now, and fixed. Thanks for the short answer.