New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setting deploy key in some cases fail with HTTP 400: {"fingerprint":["has already been taken"]} #19
Comments
Haven't seen this since #1 has been implemented. Closing it then. |
Hey. A similar problem on v4.
command:
|
Thanks @razumv ! I’ll try to reproduce it. |
I see this too on
|
I see this on GitLab |
@jccl : please try using v2. v1 is not supported anymore. Generally I still cannot reproduce this issue with the latest v2.1 and latest stable Gitlab, see https://github.com/egnyte/gitlabform/runs/2978563292?check_suite_focus=true . |
I appear to have this same issue - We are running Gitlab 14.0.5-ee , running 2.1.1 of Gitlabform. In my scenario, I created a new deploy key that I applied to a single project, then configured gitlabform to push it over a group. All projects failed, so I removed the key. I ran gitlabform again, which applied the key to one project, then failed for the remainder with HTTP 400: {"fingerprint":["has already been taken"]} Please let me know if I can provide any more detail |
Thanks @owindsor ! This may allow me to reproduce it but I have a few more questions. What do you mean by "All projects failed, so I removed the key."? Was that single project that had this key already part of that group? How did all the projects fail? How did you remove the key? |
@gdubicki The process that I followed was;
My takeaway was that the application can work (at least for a single project) so my configs and tokens were valid. |
I have checked this and frankly I am surprised that the current trivial code works at all, dealing successfully with many kinds of edge cases that you can encounter with deploy keys and failing only rarely. :/ This will require quite a lot of work to make it bullet-proof. Any volunteers? PR are welcome. |
same problem on 14.0.10-ee |
I noticed myself that the issue does still exist with the latest gitlabform. :( |
Had the same issue configuring a deploy key through the API. |
Thanks @jpiron. I noticed this again in my GitLab instance and the new SSH key does not have spaces in the comment... |
...but what you wrote about adding a comment with spaces enabled me to finally reproduce it with 100% reproducibility in a test, so thanks for that! :) Now I can work on finally getting this resolved. |
The fix in v3.3.1 resolves the issue for me. Please try it out and let me know about your results! |
For further investigation:
The text was updated successfully, but these errors were encountered: