Bug 1841350 - [buildcop] Release CI Health Dashboard is showing "This release has no current releases"
Summary: [buildcop] Release CI Health Dashboard is showing "This release has no curren...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Test Infrastructure
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.5.0
Assignee: Steve Kuznetsov
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-05-28 22:48 UTC by Ryan Phillips
Modified: 2020-06-04 15:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-06-04 15:22:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift release-controller pull 181 0 None closed Bug 1841350: Ignore releases in Ready state when calculating maxUnready 2020-09-28 23:53:57 UTC

Description Ryan Phillips 2020-05-28 22:48:40 UTC
Description of problem:
https://openshift-release.svc.ci.openshift.org/dashboards/overview is showing "This release has no current releases"

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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Thiago Alessio Pereira 2020-05-29 09:44:15 UTC
Now it shows a different message:
"This release has no recently accepted payloads, investigation required."

Comment 2 Luke Meyer 2020-05-29 14:22:08 UTC
It's currently showing that for 4.5.0-0.ci and 4.4.0-0.ci - gotta be specific, CI and nightly are handled by different groups :)

Comment 3 brad.williams 2020-05-29 15:53:43 UTC
I can find no reference to the verbiage "This release has no current releases" in the release controller source or the log file from the running controller.  The message may be an error thrown from the system when trying to read the release imagestreams.  Unfortunately, I'm not seeing it in the log files.

The other message that is typically displayed on the overview page is: "This release has no recently accepted payloads, investigation required.".  This message occurs when there are greater than "maxUnreadyReleases" for a specific release.  For 4.5.0-0.ci that value is 2.  The message is to inform the build cop that multiple failures have occurred and they should be investigated.

Im not sure there is much we'll be able to determine from the environment at this point, now that things appear to be back to running as expected.

Comment 4 brad.williams 2020-05-29 20:43:50 UTC
I have made some changes to the logic that determines when to display the "This release has no recently accepted payloads, investigation required." message in PR:
https://github.com/openshift/release-controller/pull/181

Comment 7 Steve Kuznetsov 2020-06-04 15:22:33 UTC
This works. No action needed from QE.


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