[jbosstools-issues] [JBoss JIRA] (JBIDE-12031) Hard-coded OpenShift SSH key name: libra_id_rsa

[Andre Dietisheim (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697659#comment-12697659 ] 

Andre Dietisheim edited comment on JBIDE-12031 at 5/31/12 12:56 PM:
--------------------------------------------------------------------

so from the responses we have the new cli tooling does not touch the <home>/.ssh/config any longer. it will use id_rsa instead.

We therefore switch to *id_rsa.pub* for the default (and mandatory) key name when you create a key in the domain creation wizard.
We simply warn the user about an existing <home>/.ssh/config which fixes a key to be used on an OpenShift host (which is currently *.rhcloud.com, *.dev.rhcloud.com, *.stg.rhcloud.com)

!warning-about-ssh-config.png!
                
      was (Author: adietish):
    so from the responses we have the new cli tooling does not touch the <home>/.ssh/config any longer. it will use id_rsa instead.

We therefore switch to *id_rsa.pub* for the default (and mandatory) key name when you create a key in the domain creation wizard.
We simply warn the user about an existing <home>/.ssh/config which fixes a key to be used on an OpenShift host (which is currently *.rhcloud.com, *.dev.rhcloud.com, *.stg.rhcloud.com)
                  
> Hard-coded OpenShift SSH key name: libra_id_rsa
> -----------------------------------------------
>
>                 Key: JBIDE-12031
>                 URL: https://issues.jboss.org/browse/JBIDE-12031
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: openshift
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Attila Nagy
>            Assignee: Andre Dietisheim
>            Priority: Critical
>             Fix For: 3.3.0.CR1
>
>
> Note: From the end of this sprint OpenShift will use SSH key name 'id_rsa' as a default.
> Therefore my testing environment didn't have key 'libra_id_rsa' in $HOME/.ssh directory.
> 1) Log on with a user which doesn't have domain created yet.
> 2) Create a domain in JBoss Tools and select public key '$HOME/.ssh/id_rsa.pub'
> 3) Create a new application
> Actual Result: Application is created successfully, however there's an error during cloning the repository.
> Could not clone the repository. Authentication failed.
>  Please make sure that you added your private key to the ssh preferences.
> ssh://da14555e8663461383c0e80b7aa90191@myphp2012052804-myd2012052804.dev.rhcloud.com/~/git/myphp2012052804.git/: java.io.FileNotFoundException: /home/attila/.ssh/libra_id_rsa (No such file or directory)
> Expected Result: Application must be created and cloned successfully
> Possible workaround: 
> cp $HOME/.ssh/id_rsa $HOME/.ssh/libra_id_rsa
> cp $HOME/.ssh/id_rsa.pub $HOME/.ssh/libra_id_rsa.pub

--
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