[jbosstools-issues] [JBoss JIRA] (JBIDE-11810) OpenShift port forwarding exception without ssh key
Stefan Bunciak (JIRA)
jira-events at lists.jboss.org
Wed Jun 6 11:23:20 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Bunciak closed JBIDE-11810.
----------------------------------
Closing on behalf of opening a new issue JBIDE-12118.
Verified in JBoss Developer Studio
Version: 5.0.0.CR1
Build id: v20120605-2229-H183-CR1
Build date: 20120605-2229
> OpenShift port forwarding exception without ssh key
> ---------------------------------------------------
>
> Key: JBIDE-11810
> URL: https://issues.jboss.org/browse/JBIDE-11810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.Beta3
> Reporter: Stefan Bunciak
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 3.3.0.CR1
>
> Attachments: machydraerrorportdialog.png, Screen Shot 2012-05-22 at 3.23.01 PM.png
>
>
> Stack trace:
> {code}
> com.jcraft.jsch.JSchException: Auth fail
> at com.jcraft.jsch.Session.connect(Session.java:461)
> at com.jcraft.jsch.Session.connect(Session.java:154)
> at org.jboss.tools.openshift.express.internal.ui.utils.OpenShiftSshSessionFactory.createSession(OpenShiftSshSessionFactory.java:105)
> at org.jboss.tools.openshift.express.internal.ui.utils.OpenShiftSshSessionFactory.createSession(OpenShiftSshSessionFactory.java:82)
> at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage.verifyApplicationSSHSession(ApplicationPortForwardingWizardPage.java:364)
> at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage.access$1(ApplicationPortForwardingWizardPage.java:360)
> at org.jboss.tools.openshift.express.internal.core.portforward.ApplicationPortForwardingWizardPage$4$1.run(ApplicationPortForwardingWizardPage.java:194)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
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
More information about the jbosstools-issues
mailing list