Bug 1413207

Summary: Error in changing the RSA Key of an OpenStack Director provider
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: ProvidersAssignee: Sam Lucidi <slucidi>
Status: CLOSED ERRATA QA Contact: Ola Pavlenko <opavlenk>
Severity: high Docs Contact:
Priority: high    
Version: 5.6.0CC: cpelland, dajohnso, gblomqui, jfrey, jhardy, ldomb, obarenbo, pblaho, rrasouli, slucidi, tzumainn
Target Milestone: GAKeywords: ZStream
Target Release: 5.7.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: openstack
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1376605 Environment:
Last Closed: 2017-02-27 19:23:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: Openstack Target Upstream Version:
Bug Depends On: 1376605    
Bug Blocks:    

Comment 2 CFME Bot 2017-01-16 19:30:48 UTC
New commit detected on ManageIQ/manageiq/euwe:

commit 14006476d7a126e98b0e3e9ea80ede0d44310010
Author:     Greg Blomquist <blomquisg>
AuthorDate: Fri Jan 13 14:58:24 2017 -0500
Commit:     Satoe Imaishi <simaishi>
CommitDate: Mon Jan 16 14:24:55 2017 -0500

    Merge pull request #13445 from petrblaho/openstack-infra-ssh-keypair-validation-fixes
    Openstack infra ssh keypair validation fixes
    (cherry picked from commit df1fcf14f2439523e478cbfbaf79159eb0d78333)

 .../manageiq/providers/openstack/infra_manager.rb  |  7 +++--
 spec/factories/host.rb                             |  1 +
 .../providers/openstack/infra_manager_spec.rb      | 30 ++++++++++++++++++++++
 3 files changed, 36 insertions(+), 2 deletions(-)

Comment 3 Ronnie Rasouli 2017-01-30 09:26:35 UTC
verified on - provisioned new RHOS10, the existing provider had a wrong SSH key, then selected the correct key from the new RHOS installation, the new key accepted, credentials validation passed

Comment 5 errata-xmlrpc 2017-02-27 19:23:00 UTC
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.