Bug 1004307

Summary:	Clicking "Enable Jenkins builds" causes "We appear to be having technical difficulties"
Product:	OpenShift Online	Reporter:	Dan Greaves <dangreaves92>
Component:	Website	Assignee:	Fabiano Franz <ffranz>
Status:	CLOSED WORKSFORME	QA Contact:	libra bugs <libra-bugs>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.x	CC:	dangreaves92
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-09-10 16:06:13 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:

Description Dan Greaves 2013-09-04 11:27:59 UTC

Description of problem:

When I navigate to my app in the web console and click "Enable Jenkins builds", I am redirected to a page that says "We appear to be having technical difficulties".

The reference hash displayed at the bottom of the screen is  #7698325a8c0584e4c4bd6538a4c5a1c3.

This appears to be happening in a number of other circumstances too including reducing the minimum number of gears to use in the PHP cartridge.

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

n/a

How reproducible:

I don't know whether this bug is specific to me but I simply go to the app and click "Enable Jenkins builds".

Steps to Reproduce:

1. Navigate to application
2. Click "Enable Jenkins builds"
3. Read resulting error page

Actual results:

An error page is displayed with reference #7698325a8c0584e4c4bd6538a4c5a1c3.

Expected results:

The "Enable Jenkins builds" wizard should appear.

Additional info:

n/a

Comment 1 Fabiano Franz 2013-09-10 16:06:13 UTC

Checking logs I found a 502 (proxy error) cause for #7698325a8c0584e4c4bd6538a4c5a1c3, so this was probably related to temporary outage of broker during a prod deploy. Closing this but can you please check if the error is still reproducible and if so, send the new reference id?

Comment 2 Dan Greaves 2013-09-10 17:31:13 UTC

Looks like it's working fine for me now. Might be worth outputting a bit more error information on the 502 page?

Seen as the majority (if not all) the users here are developers, I don't think that hiding error information has any benefit, especially when it comes to logging bugs.