Hide Forgot
The traced new relic exception from streamline: https://rpm.newrelic.com/accounts/411887/applications/2116199/traced_errors/1024208320 conveys no useful information about the cause of the problem. If this is an "expected" exception (i.e. auth just failed) then we shouldn't be logging this exception (the exception needs to be more specific, and then handled in handle_exception with a specific block that sets internal_error false). If this is unexpected, we need to be logging more information about what triggered it (i.e. a bad streamline response, "Unable to authenticate at this time, please try again later"). If it's being logged to new relic as is it's also showing up to a user without a message.
Proposed fix --> https://github.com/openshift/origin-server/pull/4418
Commit pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/ef8036b667a54c6787d4cbb546dab6581623976c Fix for bug 1040673
Verified on devenv_4191 Make the steamline unavailable(by updating the streamline config) and then create an application. An AuthServiceException will be logged. 2014-01-06 21:24:30.298 [DEBUG] FAILURE ACTION=LIST_DOMAIN USER_ID= LOGIN= DOMAIN= Unable to complete the requested operation due to: OpenShift::AuthServiceException. Unable to complete the requested operation due to: OpenShift::AuthServiceException. Reference ID: a6d98d1d241b91d59d40f29bcce813ee (pid:10229)