Closed andersy005 closed 5 years ago
My leading hypothesis is that not all fo the objects had their permissions set to fully open. There has also been some recent churn in s3fs but this seems more like a object read permission error.
OK, so it turns out that to grant public access I needed to not only declare the bucket public but also to make every object in the bucket publicly readable. I have launched that process and it will need to churn through everything. If you happen to be online now and want to test, try atm/monthly/FLNS because I did that one separately first.
-Jeff DLB
On Sat, Aug 31, 2019 at 4:44 PM Joe Hamman notifications@github.com wrote:
My leading hypothesis is that not all fo the objects had their permissions set to fully open. There has also been some recent churn in s3fs but this seems more like a object read permission error.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/NCAR/cesm-lens-aws/issues/2?email_source=notifications&email_token=ABF4W4X7RSTFBAPETIE45BDQHLJ4PA5CNFSM4ISUPKIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5TU4ZA#issuecomment-526863972, or mute the thread https://github.com/notifications/unsubscribe-auth/ABF4W4TF42GBCOS3QQZI6KDQHLJ4PANCNFSM4ISUPKIA .
In retrospect, the make-objects-public step should have been obvious.
Status update: 90 minutes later, only 14% through the process. I should have done this in smaller chunks because I'm not sure what will happen if my laptop goes to sleep...
-Jeff
On Sun, Sep 1, 2019 at 10:24 AM Jeff de La Beaujardière < notifications@github.com> wrote:
OK, so it turns out that to grant public access I needed to not only declare the bucket public but also to make every object in the bucket publicly readable. I have launched that process and it will need to churn through everything. If you happen to be online now and want to test, try atm/monthly/FLNS because I did that one separately first.
-Jeff DLB
On Sat, Aug 31, 2019 at 4:44 PM Joe Hamman notifications@github.com wrote:
My leading hypothesis is that not all fo the objects had their permissions set to fully open. There has also been some recent churn in s3fs but this seems more like a object read permission error.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/NCAR/cesm-lens-aws/issues/2?email_source=notifications&email_token=ABF4W4X7RSTFBAPETIE45BDQHLJ4PA5CNFSM4ISUPKIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5TU4ZA#issuecomment-526863972 , or mute the thread < https://github.com/notifications/unsubscribe-auth/ABF4W4TF42GBCOS3QQZI6KDQHLJ4PANCNFSM4ISUPKIA
.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/NCAR/cesm-lens-aws/issues/2?email_source=notifications&email_token=ABF4W4S6U6VCPJLKDAWTFJLQHPGDDA5CNFSM4ISUPKIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5UDNRA#issuecomment-526923460, or mute the thread https://github.com/notifications/unsubscribe-auth/ABF4W4RV4W3KTUTDBDPHXQTQHPGDDANCNFSM4ISUPKIA .
Thank you for taking care of this, @jeffdlb! I ran a few smoke tests, and this seems to be working
Anderson-
atm/daily and atm/hourly6-1990-2005 are still not fully public. Will be finished this morning.
-Jeff
On Mon, Sep 2, 2019 at 11:31 PM Anderson Banihirwe notifications@github.com wrote:
Thank you for taking care of this, @jeffdlb! I ran a few smoke tests, and this seems to be working
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
I believe all of the data objects are now public. Please let me know if you experience any difficulty.
-Jeff
On Tue, Sep 3, 2019 at 6:50 AM Jeff de La Beaujardiere jeffdlb@ucar.edu wrote:
Anderson-
atm/daily and atm/hourly6-1990-2005 are still not fully public. Will be finished this morning.
-Jeff
On Mon, Sep 2, 2019 at 11:31 PM Anderson Banihirwe notifications@github.com wrote:
Thank you for taking care of this, @jeffdlb! I ran a few smoke tests, and this seems to be working
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
and can be accessed anonymously. It appears that you still need to provide credentials to be able to access objects in this bucket:Cc @jhamman