You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And wrap train in tune.durable.
In cluster.yaml's setup cmd, add pip install awscli
Still the same workflow but ran into the following issue on worker: Error message (1): fatal error: Unable to locate credentials
On Driver
(base) ray@ip-172-31-24-198:~$ aws configure list
Name Value Type Location
---- ----- ---- --------
profile <not set> None None
access_key ****************2RSP iam-role
secret_key ****************S2Jm iam-role
region <not set> None None
On worker
(base) ray@ip-172-31-19-194:~$ aws configure list
Name Value Type Location
---- ----- ---- --------
profile <not set> None None
access_key <not set> None None
secret_key <not set> None None
region <not set> None None
Is this expected? Am I missing something?
Reproduction (REQUIRED)
Please provide a short code snippet (less than 50 lines if possible) that can be copy-pasted to reproduce the issue. The snippet should have no external library dependencies (i.e., use fake or mock data / environments):
If the code snippet cannot be run by itself, the issue will be closed with "needs-repro-script".
I have verified my script runs in a clean environment and reproduces the issue.
I have verified the issue also occurs with the latest wheels.
The text was updated successfully, but these errors were encountered:
xwjiang2010
added
bug
Something that is supposed to be working; but isn't
triage
Needs triage (eg: priority, bug/not-bug, and owning component)
labels
Aug 28, 2021
What is the problem?
I was just trying to see if sync to S3 works to bypass rsync issue for our customer.
The same set up as #17940, with the following change:
And wrap
train
intune.durable
.In cluster.yaml's setup cmd, add
pip install awscli
Still the same workflow but ran into the following issue on worker:
Error message (1): fatal error: Unable to locate credentials
On Driver
On worker
Is this expected? Am I missing something?
Reproduction (REQUIRED)
Please provide a short code snippet (less than 50 lines if possible) that can be copy-pasted to reproduce the issue. The snippet should have no external library dependencies (i.e., use fake or mock data / environments):
If the code snippet cannot be run by itself, the issue will be closed with "needs-repro-script".
The text was updated successfully, but these errors were encountered: