@<1523701087100473344:profile|SuccessfulKoala55> clearml-agent version is 1.6.1
yup, I'll try and let you know
Hey @<1721336583027691520:profile|ImmenseKoala11> , I have done something similar. My setup is quite a bit different since I had to handle some other internal stuff, but the general idea is the same as yours.
My startup script does a simple clearml-agent daemon --queue <my_queue> , where <my_queue> is a queue I created manually from the webapp. I don't need to change it often, so my agents simply connect to the existing queue. Also I don't have the --detatched flag, I don't think...
I confirm that I can successfully clone the repo from a newly created shell directly on the clearml agent server using the url it printed in the logs:
_company.com:1234/our_gitlab/our_repo.git
I'm using a self hosted instance of clearml, running on AWS using the AMI clearml-server-1.13.0-414-117
Good to know, thanks!
@<1523701087100473344:profile|SuccessfulKoala55> Thank your for your advice. I have updated the clearml agent version to 1.7, cleared the cached and forced the server port (it wasn't 22) and also forced the ssh user to git. The error has changed slightly:
cloning:
_company.com:1234/our_gitlab/our_repo.git
Using SSH credentials - ssh url '
_company.com:1234/our_gitlab/our_repo.git' with ssh url '
_company.com:1234/our_gitlab/our_repo.git'
git@our_to...Hi Martin, of course not, I was just wondering if it has been patched yet and if not what is the expected timeline for patching it
I managed to solve the issue by debugging the agent. I found out that despite the None _company.com:1234/our_gitlab/our_repo.git line I found out that it was actually trying to clone from the url None _company.com:1234/our_gitlab/our_repo.git . The agent host machine therefore didn't try to use the git user, but the session user ec2-user resulting in a permission denied error.
I solved it by adding an entry in the agent's `~/...
Hi everyone, me and my team are on 1.16 and we're experiencing the same credentials disappearing behaviour reported by @<1689446563463565312:profile|SmallTurkey79> . Can confirm that the issue appeared the moment we switched to 1.16.0 .
@<1689446563463565312:profile|SmallTurkey79> Did you find a way around it?
@<1523701087100473344:profile|SuccessfulKoala55> Any updates on this?