@<1600661428556009472:profile|HighCoyote66> managed to solve the issue, the git i've provided was indeed in developer role, i switched to my personal git (which is maintainer) and it works smoothly. but thanks for the help!
hey, thanks for the reply.
i understood, perhaps i was wrong, that i need to create the "scaler" queue and have an agent listening on the queue so that when i run the auto_scaler with the --remote flag someone will pick up the task.
as for the current setup question, do you mean like how my machines are configured?
what im trying to achieve is that i could instantiate ec2 clients so that we could train our networks, i want to be able to instantiate multiple instances, but also control when i turn them off, therefore the auto_scaler seems like the logical solution
Hi @<1612982606469533696:profile|ZealousFlamingo93> , I'm not sure I understand. You're trying to run the autoscaler, how is the clearml-agent
connected to this?
Can you please elaborate a bit on your setup and what you're trying to achieve?
Hey @<1612982606469533696:profile|ZealousFlamingo93> , I had a similar problem with Gitlab tokens not working with the Agent. My issue was slightly different with the error being clearly a permissions issue with no alternative options, but I see that your output is suggesting to check if your remote-worker had valid credentials as well along with the making sure you have the right commit.
I resolved the issue by making a gitlab token with a developer role. I found that with private Gitlab repos, the Guest role (which is default for Gitlab project access tokens) does not have the permission to clone or even access the repos.