[jbosstools-issues] [JBoss JIRA] (JBIDE-11429) Document how to import a SSH key for an existing openshift application
Burr Sutter (JIRA)
jira-events at lists.jboss.org
Mon May 7 10:40:20 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12690808#comment-12690808 ]
Burr Sutter commented on JBIDE-11429:
-------------------------------------
I find that with B2 - that it normally "breaks" - even though mykey.pub's contents have been uploaded to the OpenShift web UI and Eclipse seems to be pointing at the right location (e.g. C:\Users\burr\.ssh), the OpenShift Application Wizard will still fail at the end - the app is provisioned at openshift but the git clone fails.
For instance, of 10+ attempts yesterday on B2, it failed 9 out of 10 times.
We could put the various workarounds in a troubleshooting area of the JBoss Tools & OpenShift documentation. And this is a more of a JBoss Tools problem as the command line rarely fails while JBoss Tools (B2) failed more often than not.
> Document how to import a SSH key for an existing openshift application
> ----------------------------------------------------------------------
>
> Key: JBIDE-11429
> URL: https://issues.jboss.org/browse/JBIDE-11429
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Burr Sutter
> Assignee: Max Rydahl Andersen
> Fix For: 3.3.0.Beta3
>
>
> If the user has a pre-deployed application at OpenShift and he has installed JBDS/Tools on a new machine, what steps must he perform in order to get the new machine, new installation of JBDS/Tools working with pre-existing openshift applications. ssh2 key
--
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