Bug 1323793

Summary: Unable to login via the Red Hat Access module
Product: Red Hat Satellite Reporter: jcallaha
Component: RH Cloud - InsightsAssignee: Lindani Phiri <lphiri>
Status: CLOSED ERRATA QA Contact: jcallaha
Severity: urgent Docs Contact:
Priority: urgent    
Version: 6.2.0CC: bbuckingham, jcallaha, mmccune
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-foreman-redhat_access-1.0.3-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-27 09:30:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Error screenshot
none
production.log none

Description jcallaha 2016-04-04 18:00:46 UTC
Created attachment 1143406 [details]
Error screenshot

Description of problem:
While attempting to log in via the RH Access module, I am told that the login failed. The Chrome console then shows a 500 error after the request.

Version-Release number of selected component (if applicable):
Satellite 6.1 Beta Snap 6 Compose 1

How reproducible:
Always

Steps to Reproduce:
1. Attempt to log in to Red Hat Access via the UI module with the same name.
2. View results.

Actual results:
Login failed with proper credentials. 500 error seen in web console.

Expected results:
Login succeeds with proper credentials. No errors seen.

Comment 2 Lindani Phiri 2016-04-05 16:45:53 UTC
@jcallaha,

Can you provide the server side logs  (/var/log/foreman/production.log?) with the exception trace?

Thanks!

Comment 3 jcallaha 2016-04-05 17:23:10 UTC
Created attachment 1143902 [details]
production.log

Comment 4 Lindani Phiri 2016-04-05 20:25:12 UTC
Bug is caused by changes to http proxy settings handling in 6.2.
I will impact both the Insights and Red Hat Access search/case management when an http proxy is configured for the Satellite server.

Comment 8 jcallaha 2016-04-14 14:50:27 UTC
Verified in Satellite 6.2 Beta Snap 8 compose 1.

The module now works as expected.

Comment 10 errata-xmlrpc 2016-07-27 09:30:53 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.

https://access.redhat.com/errata/RHBA-2016:1501