Bug 1322416 - Error logging into self_service UI
Summary: Error logging into self_service UI
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: Appliance
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.6.0
Assignee: Oleg Barenboim
QA Contact: Shveta
URL:
Whiteboard: ssui
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-30 13:15 UTC by bascar
Modified: 2016-06-29 15:46 UTC (History)
9 users (show)

Fixed In Version: 5.6.0.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-29 15:46:06 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
javascript error log (6.23 KB, text/plain)
2016-03-30 13:15 UTC, bascar
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:1348 0 normal SHIPPED_LIVE CFME 5.6.0 bug fixes and enhancement update 2016-06-29 18:50:04 UTC

Description bascar 2016-03-30 13:15:07 UTC
Created attachment 1141747 [details]
javascript error log

Description of problem: On a new beta 1 appliance, when attempting to log into the self_service UI the progress bar goes to around 95% and then stops. Errors are caught in the browser javascript console which throws back a 500 internal service error.


Version-Release number of selected component (if applicable):
5.6.0.0-Beta 1

How reproducible: Every time and multiple reproducers.


Steps to Reproduce:
1. Log into self_service UI
2.
3.

Actual results: Not able to log in


Expected results: Able to log in


Additional info: Will attach logs from appliance and javascript error log.

Comment 7 Dave Johnson 2016-03-30 14:59:57 UTC
Right, same issue with 3 providers already added on it.  To recover, the following worked for me.

systemctl restart rh-postgresql94-postgresql.service
systemctl restart evmserverd.service

And now after running them, it seems I can login to the ssui

Comment 8 Dave Johnson 2016-03-30 16:20:25 UTC
So you can certainly login on a fresh install that has not been running, but at some point, the connection pool is exhausted and logins to the ssui (which are via rest calls) fail to work and completely cripple the appliance... still chasing.

Comment 9 bascar 2016-03-30 18:06:23 UTC
Please note, that even after doing the postgres and evmserverd restarts it behaves the exact same. Also even after a reboot of the appliance and watching the evm logs until everything is up. If immediately you log into ops UI, that is fine. You can put in bad passwords and it won't accept, correct passwords and you can login. On my test appliance however, as soon as you try and log into the SSUI and you get the errors back on the Javascript console, at that point no logins from any UI are then possible.

Comment 12 Matthew Draper 2016-04-06 23:35:17 UTC
https://github.com/rails/rails/pull/24422

Comment 13 Shveta 2016-04-16 23:47:06 UTC
Verified in 5.6.0.1-beta2.20160413141124_e25ac0e

Comment 16 errata-xmlrpc 2016-06-29 15:46:06 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:1348


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