Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1322891 - Can not validate C&U credentials for RHEVM provider
Can not validate C&U credentials for RHEVM provider
Status: CLOSED WORKSFORME
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Providers (Show other bugs)
5.6.0
Unspecified Unspecified
high Severity high
: GA
: 5.6.0
Assigned To: Greg Blomquist
Nandini Chandra
c&u:rhev
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-03-31 10:30 EDT by Alex Krzos
Modified: 2016-08-18 12:09 EDT (History)
11 users (show)

See Also:
Fixed In Version: 5.6.0.6
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-18 12:09:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 14:50:04 EDT

  None (edit)
Description Alex Krzos 2016-03-31 10:30:28 EDT
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.
Comment 2 Greg Blomquist 2016-04-07 10:42:45 EDT
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...
Comment 3 Nandini Chandra 2016-04-07 16:08:37 EDT
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.
Comment 6 Greg Blomquist 2016-05-06 15:12:10 EDT
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.
Comment 8 Chris Arcand 2016-05-11 15:49:39 EDT
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.
Comment 9 Nandini Chandra 2016-05-12 18:16:34 EDT
Verified in 5.6.0.6
Comment 11 errata-xmlrpc 2016-06-29 11:46:42 EDT
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

Note You need to log in before you can comment on or make changes to this bug.