[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10563: ------------------------------------------ looking at your screenshot I would guess that you're running JBoss Tools 3.3.0.M4. Can you please update to M5 (or a nightly) and see if you still have the very same problem? It would also help a lot if you could attach your eclipse log (<workspace>\.metadata\.log) since that could possibly tell use what you were facing. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Alex Popescu updated JBIDE-10563: --------------------------------- Attachment: .log Log File from Eclipe Workspace. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10563: ------------------------------------------ @Alex: Unfortunately I cannot spot any OpenShift related errors in the log you attached. There are some errors in your log that report failed resource deletetion. It looks like your workspace is not in sync. Did you ever try to refresh your workspace? Could you inidicate/attach the project you tried to use with OpenShift? That would allow me to try to reproduce in a manner that is hopefully closer to your setup. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10563 at 1/4/12 9:57 AM: ------------------------------------------------------------------ @Alex: Unfortunately I cannot spot any OpenShift related errors in the log you attached. There are some errors in your log that report failed resource deletetion. It looks like your workspace is not in sync. Did you ever try to refresh your workspace? Another Test you could try is to clone the OpenShift application manually: 1.) launch the OpenShift wizard & log in 2.) on the applications page: select the application you want to clone and hit the "Details"-Button. 3.) select and copy the "Git URL" & close the dialog & cancel the OpenShift wizard 4.) get to the "Git Repository Exploring" perspective and choose "Clone a Git Repository and add the clone to this view" from the "Git Repositories" view !clone-git-repository.png! 5.) Paste the "Git URL" into the "Git Uri" text field of the upcoming wizard and try to clone the OpenShift git repo manually. Please report back if this works. was (Author: adietish): @Alex: Unfortunately I cannot spot any OpenShift related errors in the log you attached. There are some errors in your log that report failed resource deletetion. It looks like your workspace is not in sync. Did you ever try to refresh your workspace? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10563 at 1/4/12 9:58 AM: ------------------------------------------------------------------ @Alex: Unfortunately I cannot spot any OpenShift related errors in the log you attached. There are some errors in your log that report failed resource deletetion. It looks like your workspace is not in sync. Did you ever try to refresh your workspace? Another Test you could try is to clone the OpenShift application manually: 1.) launch the OpenShift wizard & log in 2.) on the applications page: select the application you want to clone and hit the "Details"-Button. 3.) select and copy the "Git URL" & close the dialog & cancel the OpenShift wizard 4.) get to the "Git Repository Exploring" perspective and choose "Clone a Git Repository and add the clone to this view" from the "Git Repositories" view !clone-git-repository.png! 5.) Paste the "Git URL" into the "Git Uri" text field of the upcoming wizard and try to clone the OpenShift git repo manually. Please report back if this works. was (Author: adietish): @Alex: Unfortunately I cannot spot any OpenShift related errors in the log you attached. There are some errors in your log that report failed resource deletetion. It looks like your workspace is not in sync. Did you ever try to refresh your workspace? Another Test you could try is to clone the OpenShift application manually: 1.) launch the OpenShift wizard & log in 2.) on the applications page: select the application you want to clone and hit the "Details"-Button. 3.) select and copy the "Git URL" & close the dialog & cancel the OpenShift wizard 4.) get to the "Git Repository Exploring" perspective and choose "Clone a Git Repository and add the clone to this view" from the "Git Repositories" view !clone-git-repository.png! 5.) Paste the "Git URL" into the "Git Uri" text field of the upcoming wizard and try to clone the OpenShift git repo manually. Please report back if this works. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Alex Popescu edited comment on JBIDE-10563 at 1/4/12 1:52 PM: -------------------------------------------------------------- I have tried to clone the OpenShift application manually, after closing all the projects in my workspace, and I have the same problem. Additionally, I've created a new SSH2 Key, one with a password, using the Key Management Tool from Eclipse, changed my key from OpenShift account with this one and tried to clone the git repo manually, and with the Openshift application wizard, but I didn't got prompted to enter my password, and the problem was the same. was (Author: popalx): I have tried to clone the OpenShift application manually, after closing all the projects in my workspace, and I have the same problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10563 at 1/5/12 4:45 AM: ------------------------------------------------------------------ If manual cloning fails, too, then it's pretty obvious that the culprit is egit/ssh. Nevertheless we could cause the error by having an bogus key registeration/creation. Let us verify that... * What error were you prompted by egit when cloning manually? Is there any entry about it in your log? * You said that you created a new key on behalf of the Eclipse key tooling. I suppose that you then registered your new key in the OpenShift Web GUI, right? * Could you please double check that you have your *private* key added to the private keys in the ssh2 preferences? was (Author: adietish): If manual cloning fails, too, then it's pretty obvious that the culprit is egit/ssh. Nevertheless we could cause the error by having an bogus key registeration/creation. Let us verify that... * What error were you prompted by egit when cloning manually? Is there any entry about it in your log? * You said that you created a new key on behalf of the Eclipse key tooling. I suppose that you then registered your new key in the OpenShift Web GUI, right? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Alex Popescu commented on JBIDE-10563: -------------------------------------- * I don't get an error in the Eclipse and the log is empty. The window will not close, it will go on and on trying to clone my git repo. I have to kill eclipse. * Yes, I've registered the key with the OpenShift Web GUI. * I did double checked that. I left only the correct public key in the Eclipse SSH2 preferences window. * Yes, I have Putty, TortoiseGit and a Git command line client (that I think has also an ssh client). When trying to clone the git repo, I can find a "rogue" ssh.exe precess that is created by Eclipse (acording to Process Explorer by Sysinternals). The process does not close when I close Eclipse after trying to clone a repo. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10563 at 1/9/12 4:01 AM: ------------------------------------------------------------------ Reading your comment it pretty much looks like JSch is using the external ssh executable. The only way to force EGit/JSch to use an external SSH.EXE is to set the GIT_SSH environment variable: https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526#c9 Is this set on your system? What version is your JSch plugin in (I'd expect at least 0.1.44)? Do things work if you clear it (which should cause EGit to use the internal ssh)? was (Author: adietish): Reading your comment it pretty much looks like JSch is using the external ssh executable. The only way to force EGit/JSch to use an external SSH.EXE is to set the GIT_SSH environment variable: https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526#c9 Is this set on your system? Do things work if you clear it (which should cause EGit to use the internal ssh)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-10563 at 1/9/12 4:14 AM: ------------------------------------------------------------------ Reading your comment it pretty much looks like JSch is using the external ssh executable. The only way to force EGit/JSch to use an external SSH.EXE is to set the GIT_SSH environment variable: https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526#c9 http://stackoverflow.com/a/6316078/231357 * Is this (GIT_SSH environment variable)set on your system? * What version is your JSch plugin in (I'd expect at least 0.1.44)? * Do things work if you clear it (which should cause EGit to use the internal ssh)? was (Author: adietish): Reading your comment it pretty much looks like JSch is using the external ssh executable. The only way to force EGit/JSch to use an external SSH.EXE is to set the GIT_SSH environment variable: https://bugs.eclipse.org/bugs/show_bug.cgi?id=326526#c9 http://stackoverflow.com/a/6316078/231357 Is this set on your system? What version is your JSch plugin in (I'd expect at least 0.1.44)? Do things work if you clear it (which should cause EGit to use the internal ssh)? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10563: ------------------------------------------ * JSch looks good enough. JSch 0.1.44 should just work fine (prior versions had trouble with newer key types, especially AES128 ones). * GIT_SSH should point to your current ssh executable. Isn't it set? You should be able to run eclipse without that GIT_SSH environment variable. EGit will use the executable that this points to or use JSch if it's not set. I'd suggest that you unset GIT_SSH and try again (Eclipse EGit will then use the internal JSch which should work just fine). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Alex Popescu commented on JBIDE-10563: -------------------------------------- After unsetting the GIT_SSH environment variable I was able to clone the git repo and to edit my OpenShift Application. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-10563. -------------------------------------- Resolution: Done -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-10563?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-10563. ----------------------------------- Closing the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira