-
Notifications
You must be signed in to change notification settings - Fork 29
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
Can't run a Cilicon via Gitlab runner (Citadel.SSHClient.CommandFailed error 1.) #55
Comments
Hi @kpolupanova, to rule out potential issues with the gitlab provisioner, could you test with a |
@Marcocanc Thanks for fast answer! With scrip it's goint like this. Is it correct behaviour ? I've set up CI/CD and trying to figure out how to run my pipeline by virtual machine. |
The behaviour with
Could you explain this a bit further with more context? Do I understand it correctly, that you are able to spin up a gitlab runner on your local machine with the same runner token you were trying to use in Cilicon? |
Sure! Well, I've tried set up Cilicon with new gitlab runner that was't registred at all at Host OS machine, and got the same error, then tried to set up Cilicon with existing runner token that was registred at Host OS machine. And after all, for being sure that i don't have any problem with runner with same token, I checked that runner work correctly at Host OS machine. |
I have the same Problem here. I am trying to connect the cilicon runner to a self-hosted gitlab instance and i end up in an endless loop with the aforementioned error The cilicon.yml is And the cilicon version is 2.2.2 |
I'm seeing the same behaviour as described above. My
It seems like the issue was introduced in Cilicon v2.2.1. The runner successfully connects to GitLab if I downgrade to v2.2.0. |
@alanrickman thanks for your reply, I'll try with a downgrade, and hope that this issue will be fixed in future release |
@kpolupanova did downgrading fix the issue? |
@Marcocanc yes after downgrading everything works fine, but I hope this will be fixed in future updates |
Just wanted to mention I have the same issue. Downgrading from v2.2.2 to v2.2.0 works! |
Hi! I've tried to start workin with cilicon and get an error that I can't figure out how to fix.
After launc Cilicon i get this error:
Configuring GitLab Runner...�
The operation couldn’t be completed. (Citadel.SSHClient.CommandFailed error 1.)
here is my cilicon.yml
Could somebody tell me what I'm doing wrong ?
The text was updated successfully, but these errors were encountered: