I have a private gitlab server and two runners. They are all running the latest gitlab omnibus versions. I started running out of space on my runners in docker-in-docker builds. I brought one of the runners down, rebuilt it with double the disk space (they are all virtual anyway) and brought it back up with the same name as it had previously. Now, docker packaging runs fine (there is lots of space and they use artifacts from previous builds), but when I check out dependent projects in the actual build, I get this error on the rebuilt runner:
> git clone email@example.com:ggg/project.git …/project/
Cloning into ‘…/project’…
Host key verification failed.
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
ERROR: Build failed: exit code 1
I do not, however, get this error on the runner that I didn’t touch. It builds fine but cannot package docker due to the same space limitations. This tells me my project configuration is fine. Deploy keys were setup using gitlab’s setup instructions. I’ve tried deleting and re-registering the new runner to no avail. (It doesn’t unregister for some reason, but I can delete and re-register it just fine.)
I tried launching the docker image from the runner and running the git clone command. It asks me for the password for firstname.lastname@example.org, and I don’t know it, but it clearly can resolve the gitlab server fine. If it didn’t, it wouldn’t have asked for the password. I can also ping the gitlab server by name just fine. I don’t think connectivity is the issue.
My thought is that the gitlab server has the ssh fingerprint of the old runner cached somewhere (similar to .ssh/known_hosts), but I cannot find it for the life of me. None of the users on the runner have anything of consequence in the known_hosts, btw.
Anyone have any thoughts on this? Or know where that fingerprint would be stored?