verified on 5.7.1.0 - 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
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://rhn.redhat.com/errata/RHSA-2017-0320.html