Bug 1841350
Summary: | [buildcop] Release CI Health Dashboard is showing "This release has no current releases" | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Ryan Phillips <rphillips> |
Component: | Test Infrastructure | Assignee: | Steve Kuznetsov <skuznets> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.4 | CC: | aos-bugs, brad.williams, jokerman, talessio, wking |
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-06-04 15:22:33 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: | |
Embargoed: |
Description
Ryan Phillips
2020-05-28 22:48:40 UTC
Now it shows a different message: "This release has no recently accepted payloads, investigation required." 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 :) 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. 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 This works. No action needed from QE. |