Description of problem: Added RHEVM provider to 5.6.0.0-beta1 appliance and attempted to add C&U credentials through automation. C&U credentials fail to validate thus automation stops. The same provider + credentials works in 5.5.3.2. Version-Release number of selected component (if applicable): 5.6.0.0-beta1 How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: evm.log output: [----] W, [2016-03-31T10:24:28.431629 #60095:4c90b7c] WARN -- : MIQ(ManageIQ::Providers::Redhat::InfraManager#authentication_check_no_validation) type: ["metrics"] for [] [rhevm-small] Validation failed: invalid, Login failed due to a bad username or password. [----] E, [2016-03-31T10:24:28.431868 #60095:4c90b7c] ERROR -- : MIQ(ems_infra_controller-create): Credential validation was not successful: Login failed due to a bad username or password.
Dave, can QE reproduce this? I wonder if this is the Rails5 + RHEV data warehouse Postgresql version problem. Namely, the fact that Rails5 should only work with Postgresql 9.1 and RHEV 3.x install with Postgresql 8.0. However, the error message (Login failed due to a bad username or password) makes me think that maybe there's something else going on there...
I did run into this issue last week and have been meaning to update this BZ. This is all I see in the evm.log file. [----] W, [2016-04-07T14:14:22.286197 #3022:d319a4] WARN -- : MIQ(ManageIQ::Providers::Redhat::InfraManager#authentication_check_no_validation) type: ["metrics"] for [1] [rhevm35] Validation failed: invalid, Lo gin failed due to a bad username or password. [----] E, [2016-04-07T14:14:22.286594 #3022:d319a4] ERROR -- : MIQ(ems_infra_controller-update): Credential validation was not successful: Login failed due to a bad username or password.
https://github.com/ManageIQ/manageiq/pull/8382 .. I'm hoping this fixes the problem. Actually https://github.com/ManageIQ/ovirt_metrics/pull/10, but PR 8382 pulls the new version of ovirt_metrics into ManageIQ. Fingers crossed.
The changes Greg mentions above should fix metrics collection, as well as changes that were merged *today* in Rails related to database connection adapters. Try a fresh build with today's changes and let me know if it still doesn't work.
Verified in 5.6.0.6
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:1348