Bug 1819457

Having a very similar situation to this on an OpenShift cluster installed using IPI on the IBM Cloud last week.

OCP 4.3.12 was installed initially - since upgraded to 4.3.18 and seems to be operating normally otherwise.

There is 1 thing I'm seeing that is not listed in this bug:  The Control Plane is listed as "Not Available" on the Administrator Dashboard.
Is that caused by this bug also or do I have another problem? 

Thanks

>  The Control Plane is listed as "Not Available" on the Administrator Dashboard.

That indicates a more fundamental problem - in general, cluster components being unavailable (discovery in particular) can cause packageserver to report unhealthy, because OLM uses discovery to confirm the health of the apiservice.

Given that the objects in the current report show that the packageserver is healthy and we haven't heard back, I'm going to close this again. Please re-open with additional information describing the failure if one still exists (it is not apparent that there is an error from the current report).

I find the fixed PR only for the packageserver ownerReferences issue. And, only one ownerReferences uid, LGTM, I'm going to verify this 4.7 bug. 

1, Create the 4.7 cluster
[root@preserve-olm-env data]# oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.7.0-0.nightly-2020-11-11-033756   True        False         78m     Cluster version is 4.7.0-0.nightly-2020-11-11-033756
[root@preserve-olm-env data]# oc adm release info registry.svc.ci.openshift.org/ocp/release:4.7.0-0.nightly-2020-11-11-033756 --commits|grep lifecycle
  operator-lifecycle-manager                     https://github.com/operator-framework/operator-lifecycle-manager            161c86b215ceae325d7bf8f7f351406a0303ca27

2, Check the packageserver service
[root@preserve-olm-env data]# oc api-resources|grep packages
packagemanifests                                       packages.operators.coreos.com         true         PackageManifest

[root@preserve-olm-env data]# oc get service packageserver-service -n openshift-operator-lifecycle-manager -o yaml
apiVersion: v1
kind: Service
metadata:
...
  ownerReferences:
  - apiVersion: operators.coreos.com/v1alpha1
    blockOwnerDeletion: false
    controller: false
    kind: ClusterServiceVersion
    name: packageserver
    uid: 443dba6c-1561-4e30-8faa-f4c0fdd4b9d3
  resourceVersion: "8082"
  selfLink: /api/v1/namespaces/openshift-operator-lifecycle-manager/services/packageserver-service
  uid: 48e27560-80b7-4116-a6d3-dac24cce9bcc

[root@preserve-olm-env data]# oc get csv -n openshift-operator-lifecycle-manager packageserver -o yaml
apiVersion: operators.coreos.com/v1alpha1
kind: ClusterServiceVersion
...
  name: packageserver
  namespace: openshift-operator-lifecycle-manager
  resourceVersion: "59704"
  selfLink: /apis/operators.coreos.com/v1alpha1/namespaces/openshift-operator-lifecycle-manager/clusterserviceversions/packageserver
  uid: 443dba6c-1561-4e30-8faa-f4c0fdd4b9d3
...

3, The upgrade to 4.7 from 4.6 works well. I couldn't reproduce the origin issue. Please let me if I missed something, thanks!

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.0 security, bug fix, and enhancement 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-2020:5633

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days