-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ssh: delete key pair not working #14332
Comments
I tried both methods, generating ssh key for all hosts and particular host, and nothing works, always get:
The issue is that the host ip changed and i can't re-generate the key for the new host |
I think it is because of the known_hosts is not updated by the IDE. Can you do the initial git clone from the command line and see if git works afterwards ? |
Yes, i did try that, same problem |
Is ssh delete key generally works? Or is it buggy? |
Delete has worked for me but you may want to restart your workspace after adding/removing ssh keys. Che keeps SSH keys as k8s secrets and mounts them to the proper path so path to the key will not be removed until the restart. |
@vinokurig could you please confirm that restart is required for deleting ssh? should we add a similar warning as we currently have for ssh key generation (e.g. ssh keys will be removed after workspace restart)? |
Restart doesnt fix anything, infact clicking delete ssh key doesnt do anything as well |
@vparfonov can you check if this is a regression? |
Vitalli is on PTO, @azatsarynnyy could you please take a look? |
I believe the issue is caused by the missing entry for a remote host in
Make sure that |
@azatsarynnyy All the calls to delete/view ssh keys are failing at the moment. Here is what I see from the logs
|
I am elevating the severity of the issue. |
@azatsarynnyy I'll try your suggestion soon, I am deploying a new environment now |
Some notes after investigating an issue of deleting a key pair. Looks odd that request for generating a key pair is always successful but fetching a key is failed.
Note, not reproducible on minikube but on hosted Che only. |
@azatsarynnyy according to the issue reporter the issue was reproduced on k8s environment. Why do you think it is Hosted Che specific? |
@azatsarynnyy but che.openshift.io is still RC 1.1 - I'm not sure it is fair to compare it with master ;-) |
This is not hosted Che specific. I think this is an issue on any multi-user Che installation but for me it is reproducible on every Openshift 4.x cluster. And yes they are all multi-user installs |
Yes, reproduced the bug on minikube with multiuser Che, investigating ... |
I just deployed a new che installation just now, i can't seem to find |
No luck:
|
I am currently using |
@vinokurig : is this issue fixed? And do you know when I can get the fix? |
@SDAdham It is fixed, It must be applied in the |
@vinokurig : the image of my che's container is
None of them could get this fix any sooner, right? |
Unfortunately no |
Describe the bug
When creating a new workspace with git projects added, they don't get cloned upon workspace creation:
trying to delete a key that was generated, it's not working
Deleted it manually via k8s secretes and tried to generate a new one but i can't anymore
Che version
Steps to reproduce
A newly deployed che environment today
followed the steps of https://www.eclipse.org/che/docs/che-7/version-control/
Expected behavior
Runtime
kubectl version
)oc version
)minikube version
andkubectl version
)minishift version
andoc version
)docker version
andkubectl version
)Screenshots
Installation method
Environment
Private cloud
Additional context
The text was updated successfully, but these errors were encountered: