Bug 1088080 - INT status page shows "Test issue 1" instead of "No open issue"
Summary: INT status page shows "Test issue 1" instead of "No open issue"
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Online
Classification: Red Hat
Component: Website
Version: 2.x
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: Jessica Forrester
QA Contact: libra bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-16 02:49 UTC by Tian Feng
Modified: 2015-05-15 01:33 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-15 15:29:37 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot (66.49 KB, image/png)
2014-04-16 02:49 UTC, Tian Feng 		no flags Details
View All

Description Tian Feng 2014-04-16 02:49:08 UTC 
Created attachment 886739 [details]
screenshot

Description of problem:
Check https://int.openshift.redhat.com/app/status and got open issue "Test issue 1". The status page should show "No open issue" after each deployment. Detail can be found in attachment.

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

How reproducible:
Always

Steps to Reproduce:
1. Check status page on INT https://int.openshift.redhat.com/app/status
2. 
3.

Actual results:
The status page shows "Test issue 1" on INT.

Expected results:
The status page should show "No open issue".

Additional info:
Comment 1 Stefanie Forrester 2014-04-16 16:58:16 UTC 
The config changes have not yet made it into INT, so rhc-outage push is still failing. I've added the changes to the INT branch for release 2.0.43, which will make it into INT later today. I closed the issue and manually synced up the two brokers' status db's, so the app/status page now shows "No open issue".
Comment 2 Troy Dawson 2014-04-17 19:43:21 UTC 
Changes are in INT, and appears to be working.
Comment 3 Peter Ruan 2014-04-17 22:47:38 UTC 
verified with the latest INT image.
Note You need to log in before you can comment on or make changes to this bug.