New commit detected on ManageIQ/manageiq-ui-classic/ivanchuk: https://github.com/ManageIQ/manageiq-ui-classic/commit/134be1a7aea74ae3900773396fccf2cf0f2a5983 commit 134be1a7aea74ae3900773396fccf2cf0f2a5983 Author: Milan Zázrivec <mzazrivec> AuthorDate: Fri Aug 30 04:26:11 2019 -0400 Commit: Milan Zázrivec <mzazrivec> CommitDate: Fri Aug 30 04:26:11 2019 -0400 Merge pull request #5977 from gekorob/hostkey_mismatch_with_no_previous_validation Credentials parameters need to be serialized (cherry picked from commit 7590649175dbcb5699adb89f4e7e2b84d47ef784) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1767881 app/controllers/host_controller.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
hey, I'm having troubles verifying this BZ on 5.11.1.0.20191105221526_f1764d4. I follow the steps in the UI and I got error in the UI: Unexpected response returned from system, see log for details Here's the part of the log about this error. [----] E, [2019-11-13T07:20:17.565394 #7292:2ad0936a7d84] ERROR -- : MIQ(ManageIQ::Providers::Redhat::InfraManager::Host#connect_ssh) SSH connection failed for [*hostname*] with [NameError: uninitialized constant OpenSSL::Digest::DSS1] [----] W, [2019-11-13T07:20:17.565546 #7292:2ad0936a7d84] WARN -- : MIQ(ManageIQ::Providers::Redhat::InfraManager::Host#verify_credentials_with_ssh) #<NameError: uninitialized constant OpenSSL::Digest::DSS1> [----] E, [2019-11-13T07:20:17.566268 #7292:2ad0936a7d84] ERROR -- : MIQ(host_controller-update): Unexpected response returned from system, see log for details Just for the test, I tried to verify credentials for the same host on 5.10.12.3.20191029180220_f883bde and it worked, so it doesn't look like the problem is with the host itself. Are there any other steps?
I also provisioned new 5.11.1.0 and added the same RHV provider and tried to validate credentials of the host and it failed with the same error. (I haven't tried to change anything on the host).
Does this ticket need to be turned into a Documentation BZ or can it be closed?
Fixed and verified in 5.11.1.0.20191105221526_f1764d4.
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/RHSA-2019:4201