6:33 a.m.
Attila Nagy created JBIDE-12031:
-----------------------------------
Summary: 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
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
4:09 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12031:
----------------------------------------
Fix Version/s: 3.3.0.CR1
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
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
4:09 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12031:
------------------------------------------
this is a very serious issue, we have to verify what's going on and to decide whether
this has to be fixed before we go final with CR1
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
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
4:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim edited comment on JBIDE-12031 at 5/29/12 5:29 AM:
-------------------------------------------------------------------
Thanks for reporting! It's actually a pitty that we were not informed about this
upcoming change. We'd love to get involved into things that potentially break us.
This is a very serious issue, we have to verify what's going on and to decide whether
this has to be fixed before we go final with CR1
was (Author: adietish):
this is a very serious issue, we have to verify what's going on and to decide
whether this has to be fixed before we go final with CR1
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
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
4:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12031:
---------------------------------------------
for review - could it be cli's that renames the keys so they dissapear ?
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
4:36 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12031:
----------------------------------------
Priority: Critical (was: Major)
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
4:53 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Attila Nagy commented on JBIDE-12031:
-------------------------------------
The libra_id_rsa SSH key-pair is not renamed. It remains at the same place.
(And normally everything will work well - as $HOME/.ssh/config will contain the old
configuration,
so git will use the proper key-pair to clone application's repository)
However when a new user will create a domain name in the command line there will be
no libra_id_rsa key generated.
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
5:34 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12031:
---------------------------------------------
Attila, okey, what wonders me then is how you got a libra_id_rsa key not found exception.
How did it get added if you did not use the tools to create this domain and add the key ?
if there was a ~/.ssh/config file you should be getting an 'auth error' or
something similar - not a file not found exception.
Any chance that you did use the CLI and/or used old eclipse workspace with old settings or
something ?
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
7:04 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12031:
---------------------------------------------
From ircchat: " i know what the problem is! earlier openshift
command line tools modified $HOME/.ssh/config file to use key libra_id_rsa key."
So the reason this weird error about filenotfoundexception was not because of the tools
but because of the old ssh configuration being wrong.
This still leaves us with the hardcoding of the keyname, but that is a simpler problem to
solve ;)
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
7:08 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Attila Nagy commented on JBIDE-12031:
-------------------------------------
New OpenShift CLI wizard doesn't touch $HOME/.ssh/config, so this problem affects old
openshift users only who already had key configuration in their local SSH config file.
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
7:14 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12031:
---------------------------------------------
Mailed openshift dev following questions to know how to best fix this:
1) will the rhc client *always* use id_rsa as their name or is there a way to control the
generated key name ?
2) what happens if a user already have id_rsa installed ? will you upload it ?
3) will rhc clients still create ~/.ssh/config file since if id_rsa is the default then
its not needed anymore - what if #1 allows custom name ? does it generate ~/.ssh/config
then ?
we'll see what the answer will be.
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
11:54 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12031:
------------------------------------------
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
11:56 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
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
11:58 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12031:
-------------------------------------
Attachment: warning-about-ssh-config.png
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
Attachments: warning-about-ssh-config.png
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
12:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12031:
-------------------------------------
Attachment: use-id-rsa-by-default.patch
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
Attachments: use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
4:20 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12031:
-------------------------------------
Attachment: use-id-rsa-by-default-2.patch
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default.patch,
warning-about-ssh-config.png
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
4:20 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12031:
------------------------------------------
new patch attached, solved the bug where ssh private keys were not loaded on a fresh
workspace.
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default.patch,
warning-about-ssh-config.png
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
4:22 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12031:
-------------------------------------
Attachment: use-id-rsa-by-default-2.patch
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default.patch,
warning-about-ssh-config.png
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
4:50 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12031:
------------------------------------------
@Max: new patch attached, please review
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: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default.patch,
warning-about-ssh-config.png
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
4:52 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12031:
-------------------------------------
Attachment: use-id-rsa-by-default-3.patch
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: Max Rydahl Andersen
Priority: Critical
Fix For: 3.3.0.CR1
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
5:25 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12031:
----------------------------------------
Assignee: Andre Dietisheim (was: Max Rydahl Andersen)
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
5:25 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12031:
---------------------------------------------
i'm +1 this - handles the new defaults and old ones better than before.
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
5:54 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12031:
------------------------------------------
- removed requirement for passphrease when creating a new key
@Max: new patch attached. please review.
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
5:54 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12031:
-------------------------------------
Attachment: use-id-rsa-by-default-4.patch
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
6:11 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-12031:
---------------------------------------------
patch is good.
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
6:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim commented on JBIDE-12031:
------------------------------------------
committed to TRUNK (3.4.x) and BRANCH (3.3.0.CR1)
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
6:18 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim resolved JBIDE-12031.
--------------------------------------
Resolution: Done
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
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
10:24 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-12031:
-------------------------------------
Release Notes Text: The former incarnation of the rhc command line tools used a fixed
key name when doing ssh connections. The ssh configuration was hard coding libra_id_rsa
(in <home>/.ssh/config) for ssh-connections to OpenShift. The new version of the rhc
command line tools dont hard code keys any longer. It will use the existing libra_id_rsa
key if it exists and suggest using rsa_id if not. Our tooling now does the same.
Labels: new_and_noteworthy (was: )
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
Labels: new_and_noteworthy
Fix For: 3.3.0.CR1
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
8:42 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Isaac Rooskov updated JBIDE-12031:
----------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Writer: irooskov
Release Notes Text:
Only customers who downloaded and used the Beta releases of JBoss Developer Studio 5 may
have noticed this issue, that has since been resolved.
The former incarnation of the rhc command line tools used a fixed key name for SSH
connections. The SSH configuration contained libra_id_rsa hard coded into the file
/user/.ssh/config for SSH connections to OpenShift. This caused issues for users who
already used a different SHH configuration. The rhc command line tools no longer include
hard code keys, and instead uses the existing libra_id_rsa key or suggests using rsa_id if
a key does not exist. This behaviour has been replicated in the tooling.
was:The former incarnation of the rhc command line tools used a fixed key name when
doing ssh connections. The ssh configuration was hard coding libra_id_rsa (in
<home>/.ssh/config) for ssh-connections to OpenShift. The new version of the rhc
command line tools dont hard code keys any longer. It will use the existing libra_id_rsa
key if it exists and suggest using rsa_id if not. Our tooling now does the same.
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
Labels: new_and_noteworthy
Fix For: 3.3.0.CR1
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
7:54 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Stefan Bunciak closed JBIDE-12031.
----------------------------------
Verified in JBoss Developer Studio
Version: 5.0.0.CR1
Build id: v20120605-2229-H183-CR1
Build date: 20120605-2229
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
Labels: new_and_noteworthy
Fix For: 3.3.0.CR1
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
1:57 p.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-12031:
----------------------------------------
Release Notes Text:
Only customers who downloaded and used the Beta releases of JBoss Developer Studio 5 may
have noticed this issue, that has since been resolved.
The former incarnation of the rhc command line tools used a fixed key name for SSH
connections. The SSH configuration contained libra_id_rsa hard coded into the file
~/.ssh/config for SSH connections to OpenShift. This caused issues for users who already
used a different SHH configuration. The rhc command line tools no longer include hard code
keys, and instead uses the existing libra_id_rsa key or suggests using rsa_id if a key
does not exist. This behaviour has been replicated in the tooling.
was:
Only customers who downloaded and used the Beta releases of JBoss Developer Studio 5 may
have noticed this issue, that has since been resolved.
The former incarnation of the rhc command line tools used a fixed key name for SSH
connections. The SSH configuration contained libra_id_rsa hard coded into the file
/user/.ssh/config for SSH connections to OpenShift. This caused issues for users who
already used a different SHH configuration. The rhc command line tools no longer include
hard code keys, and instead uses the existing libra_id_rsa key or suggests using rsa_id if
a key does not exist. This behaviour has been replicated in the tooling.
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
Labels: new_and_noteworthy
Fix For: 3.3.0.CR1
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
7:18 a.m.
[
https://issues.jboss.org/browse/JBIDE-12031?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen resolved JBIDE-12031.
-----------------------------------------
Release Notes Text:
Only customers who downloaded and used the Beta releases of JBoss Developer Studio 5 may
have noticed this issue, that has since been resolved.
The former incarnation of the rhc command line tools used a fixed key name for SSH
connections. The SSH configuration contained libra_id_rsa hard coded into the file
~/.ssh/config for SSH connections to OpenShift. This caused issues for users who already
used a different SHH configuration. The rhc command line tools no longer include hard code
keys, and instead uses the existing libra_id_rsa key or suggests using rsa_id if a key
does not exist. This behaviour has been replicated in the tooling.
was:
Only customers who downloaded and used the Beta releases of JBoss Developer Studio 5 may
have noticed this issue, that has since been resolved.
The former incarnation of the rhc command line tools used a fixed key name for SSH
connections. The SSH configuration contained libra_id_rsa hard coded into the file
~/.ssh/config for SSH connections to OpenShift. This caused issues for users who already
used a different SHH configuration. The rhc command line tools no longer include hard code
keys, and instead uses the existing libra_id_rsa key or suggests using rsa_id if a key
does not exist. This behaviour has been replicated in the tooling.
Resolution: Done
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
Labels: new_and_noteworthy
Fix For: 3.3.0.CR1
Attachments: use-id-rsa-by-default-2.patch, use-id-rsa-by-default-3.patch,
use-id-rsa-by-default-4.patch, use-id-rsa-by-default.patch, warning-about-ssh-config.png
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
5040
days inactive
5061
days old
jbosstools-issues@lists.jboss.org
32 comments
5 participants
participants (5)
-
Andre Dietisheim (JIRA) -
Attila Nagy (JIRA)
-
Isaac Rooskov (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Stefan Bunciak (JIRA)