Description of problem: Typo in the UI. 'shh' should be 'SSH'. Version-Release number of selected component (if applicable): 5.4.0.0.24.20150427192818_1fd9e49 How reproducible: 100% Steps to Reproduce: 1. Navigate to Infrastructure → Providers. 2. Click (Configuration), then click (Add a New Infrastructure Provider). 3. Select 'OpenStack Infrastructure' under Type. 4. Click the RSA key pair tab under Credentials. Actual results: Note at the bottom of the tab says: Used for shh connection to all Hosts in this provider. Expected results: Note at the bottom of the tab should say: Used for SSH connection to all hosts in this provider. Additional info:
https://github.com/ManageIQ/manageiq/pull/2844
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/f841b92287e2c1f959c69490a28fe39682bd2937 commit f841b92287e2c1f959c69490a28fe39682bd2937 Author: Greg Blomquist <gblomqui> AuthorDate: Tue May 5 13:48:21 2015 -0400 Commit: Greg Blomquist <gblomqui> CommitDate: Tue May 5 14:23:16 2015 -0400 Change shh to ssh in view Also, update the translation file to change shh to ssh https://bugzilla.redhat.com/show_bug.cgi?id=1217680 vmdb/app/views/layouts/_multi_auth_credentials.html.haml | 2 +- vmdb/config/locales/manageiq.pot | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
https://github.com/ManageIQ/manageiq/pull/2850
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/f0636dcc303190f44323644cc5c8f77c090274a5 commit f0636dcc303190f44323644cc5c8f77c090274a5 Author: Oleg Barenboim <chessbyte> AuthorDate: Tue May 5 17:21:35 2015 -0400 Commit: Oleg Barenboim <chessbyte> CommitDate: Tue May 5 17:21:35 2015 -0400 Change ssh to SSH in view Also, update the translation file to change ssh to SSH https://bugzilla.redhat.com/show_bug.cgi?id=1217680 vmdb/app/views/layouts/_multi_auth_credentials.html.haml | 2 +- vmdb/config/locales/manageiq.pot | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
Greg - this probably made it into CFME 5.4 and was never flipped to POST.
Verified in 5.5.2.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:0159