[
https://issues.jboss.org/browse/JBIDE-10032?page=com.atlassian.jira.plugi...
]
Andre Dietisheim updated JBIDE-10032:
-------------------------------------
Steps to Reproduce:
ASSERT: have keys listed in the private keys in the ssh2-preferences
EXECUTE: create a new key for openshift in the domain wizard
EXECUTE: check what keys are listed in the ssh2-preferences. You should have the ones you
had before you created a new key and the new key
Result:
The ssh2 preferences only list the new key - the one you created in the step above (the
former keys were removed).
Expected:
The wizard only adds the new key, does not affect the private keys that were listed in the
ssh2 preferences.
was:
ASSERT: have keys listed in the private keys in the ssh2-preferences
EXECUTE: create a new key for openshift in the domain wizard
EXECUTE: check what keys are listed in the ssh2-preferences. You should have the ones you
had before you created a new key and the new key
Result:
The ssh2 preferences only lists the new key you just created (the former keys were
removed).
Expected:
The wizard only adds the new key, does not affect the private keys that were listed in the
ssh2 preferences.
ssh keys seem to be nuked when creating new key
-----------------------------------------------
Key: JBIDE-10032
URL:
https://issues.jboss.org/browse/JBIDE-10032
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Reporter: Max Rydahl Andersen
Assignee: Andre Dietisheim
Priority: Critical
Fix For: 3.3.0.M4
Attachments: fallback-to-defaultscope.patch, minimalistic-2.patch,
minimalistic-3.patch, minimalistic-4.patch, minimalistic.patch
--
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