Bug 1962302 - packageserver clusteroperator does not set reason or message for Available condition
Summary: packageserver clusteroperator does not set reason or message for Available co...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.7.z
Assignee: Ben Luddy
QA Contact: Jian Zhang
URL:
Whiteboard:
Depends On: 1955761 1973450
Blocks: 1963139
TreeView+ depends on / blocked
 
Reported: 2021-05-19 17:25 UTC by Ben Luddy
Modified: 2021-06-18 16:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1955761
Environment:
[bz-OLM] clusteroperator/operator-lifecycle-manager-packageserver should not change condition/Available
Last Closed: 2021-06-01 04:50:27 UTC
Target Upstream Version:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github operator-framework operator-lifecycle-manager pull 2168 0 None open [release-4.7] Bug 1962302: Set reason/message for Available condition in packageserver co 2021-05-19 17:25:45 UTC
Red Hat Product Errata RHSA-2021:2121 0 None None None 2021-06-01 04:50:42 UTC

Comment 2 Jian Zhang 2021-05-24 01:14:17 UTC 
Still no reason message in the fail status: https://search.ci.openshift.org/?search=clusteroperator%2Foperator-lifecycle-manager-packageserver+condition%2FAvailable+status%2FFalse&maxAge=24h&context=1&type=junit&name=4%5C.7&excludeName=&maxMatches=5&maxBytes=20971520&groupBy=job

I didn't find the fixed PR in the downstream repo: https://github.com/openshift/operator-framework-olm/blob/release-4.7/staging/operator-lifecycle-manager/pkg/lib/operatorstatus/builder.go#L60
Comment 7 errata-xmlrpc 2021-06-01 04:50:27 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.13 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2021:2121
Note You need to log in before you can comment on or make changes to this bug.