Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1816184

Summary: disconnected community catalog always restart because healthcheck failed
Product: OpenShift Container Platform Reporter: Nick Hale <nhale>
Component: OLMAssignee: Nick Hale <nhale>
OLM sub component: OLM QA Contact: yhui
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: high CC: dmesser, ecordell, jiazha, nhale, zhengwan
Version: 4.3.zKeywords: UpcomingSprint
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: x86_64   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1815957
: 1816185 (view as bug list) Environment:
Last Closed: 2020-05-26 16:50:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1815957    
Bug Blocks: 1816185    

Comment 7 yhui 2020-05-18 08:34:52 UTC 
[root@preserve-olm-env 1816184]# oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.4.0-0.nightly-2020-05-17-221856   True        False         4h30m   Cluster version is 4.4.0-0.nightly-2020-05-17-221856
[root@preserve-olm-env 1816184]# oc exec catalog-operator-75ddb884f8-khmfw -n openshift-operator-lifecycle-manager -- olm --version
OLM version: 0.14.2
git commit: f8ef76c241abfeeb45fa680599b9c683ec3173cf

Steps to test:
1. install ocp 4.4 cluster on azure (not aws)
2. create the community catalog source on the cluster

cat <<EOF > community-operator-catalog.yaml
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: community-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: Community Operator Catalog
  sourceType: grpc
  image: docker.io/wangzheng422/operator-catalog:community-2020-02-29
  publisher: Community
EOF
oc create -f community-operator-catalog.yaml


3. check the pod status
[root@preserve-olm-env 1816184]# oc get pod -n openshift-marketplace
NAME                                    READY   STATUS    RESTARTS   AGE
certified-operators-75bd4b8cbb-g9dz7    1/1     Running   0          24m
community-operator-catalog-9xkth        1/1     Running   0          9m34s
community-operators-66db4f7988-b6dt6    1/1     Running   0          4h25m
marketplace-operator-67955fdcc8-qldj6   1/1     Running   0          4h26m
qe-app-registry-6556d489b8-m2bg9        1/1     Running   0          4h16m
redhat-marketplace-66bd56599-lwxb9      1/1     Running   0          4h25m
redhat-operators-58b7fcd7c5-f6pkh       1/1     Running   0          84m
[root@preserve-olm-env 1816184]# oc logs community-operator-catalog-9xkth -n openshift-marketplace
time="2020-05-18T08:23:22Z" level=info msg="serving registry" database=/bundles.db port=50051

The pod didn't restart. Verify the bug.
Comment 9 errata-xmlrpc 2020-05-26 16:50:30 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, 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/RHBA-2020:2180