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
Describe the bug
The TF and Pytorch Worker Container could not automatically authenticate at the rest api via the endpoint ...api/v1/auth/login. Curling the /health endpoint showed "healthy" though. I figured it was due to the following: the worker couldn't auth with his 'username' and 'password' found in .env. So it seemed like the worker.usrname and worker.pw was not deposited at the rest api or db.
The Idea came when I create a User via WebUI and specify the name as "dioptra-worker" and pw as "{pw found in .env}" the worker container could suddenly reach every endpoint and authenticate.
Since i already continued working on enqueuing Jobs I have no screenshot or accurate error message. If needed I can reproduce the error and provide more detailed Information.
Expected behavior
An 404 error url not found!
The text was updated successfully, but these errors were encountered:
Describe the bug
The TF and Pytorch Worker Container could not automatically authenticate at the rest api via the endpoint ...api/v1/auth/login. Curling the /health endpoint showed "healthy" though. I figured it was due to the following: the worker couldn't auth with his 'username' and 'password' found in .env. So it seemed like the worker.usrname and worker.pw was not deposited at the rest api or db.
The Idea came when I create a User via WebUI and specify the name as "dioptra-worker" and pw as "{pw found in .env}" the worker container could suddenly reach every endpoint and authenticate.
Since i already continued working on enqueuing Jobs I have no screenshot or accurate error message. If needed I can reproduce the error and provide more detailed Information.
Expected behavior
An 404 error url not found!
The text was updated successfully, but these errors were encountered: