[ https://issues.jboss.org/browse/JBIDE-16102?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16102: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have an application running on OpenShift # ASSERT: make sure that you *DONT* have the correct ssh key listed in SSH preferences (Window->Preferences->General->Network Connections->SSH2->Private Keys) # EXEC: in OpenShift Explorer: select your application and pick *Port Forwarding* from the context menu Result: !ssh-failed.png! the error pops up as expected, but the error dialog is utterly verbose. It should only name the application name that we could not connect to via ssh. Expected result: It should only name the application name that we could not connect to via ssh. was: # ASSERT: make sure that you have an application running on OpenShift # ASSERT: make sure that you *DONT* have the correct ssh key listed in SSH preferences (Window->Preferences->General->Network Connections->SSH2->Private Keys) # EXEC: in OpenShift Explorer: select your application and pick *Prot Forwarding* from the context menu Result: !ssh-failed.png! the error pops up as expected, but the error dialog is utterly verbose. It should only name the application name that we could not connect to via ssh. Expected result: It should only name the application name that we could not connect to via ssh. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira