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

Bug 1761871

Summary: Subscriptions are not getting processed / take very long to get processed
Product: OpenShift Container Platform Reporter: Daniel Messer <dmesser>
Component: OLMAssignee: Evan Cordell <ecordell>
OLM sub component: OLM QA Contact: Bruno Andrade <bandrade>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: agreene, jiazha, scolange
Version: 4.1.z   
Target Milestone: ---   
Target Release: 4.3.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1763838 1763841 (view as bug list) Environment:
Last Closed: 2020-01-23 11:07:31 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:
Bug Depends On:    
Bug Blocks: 1763838, 1763841    

Description Daniel Messer 2019-10-15 13:30:53 UTC
Description of problem:

Some Subscriptions are not processed by the OLM operators. They do not receive a status block or only after an unreasonable amount of time (10-15 minutes). 


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

OCP 4.1.18


How reproducible:

The issue can be observed by repeatedly installing Operators from the same catalog, e.g. in an attempt to manually satisfy all the dependencies of OpenShift Service Mesh: Elastic Search, Jaeger, Kiali.


Steps to Reproduce:
1. Install ElasticSearch
2. Subscription get's created, processing takes about 1 minute
3. Pod `installed-redhat-openshift-operators-65d87d7cb9-tpvp4` appears in `openshift-marketplace` namespace as a result of the CatalogSourceConfig in `openshift-operators` namespace
4. Install Jaeger
5. Observe that no status block gets added to the Jaeger subscription
6. Pod `installed-redhat-openshift-operators-65d87d7cb9-tpvp4` gets killed
7. Pod `installed-redhat-openshift-operators-5d66657866-htj7k` appears instead in `openshift-marketplace`
8. OLM catalog operators log:

```
E1015 13:28:10.469041       1 queueinformer_operator.go:186] Sync "openshift-operators" failed: {jaeger-product stable jaeger-operator.v1.13.1 {installed │
│ -redhat-openshift-operators openshift-operators}} not found: rpc error: code = Unknown desc = no bundle found for csv jaeger-operator.v1.13.1             │
│ time="2019-10-15T13:28:14Z" level=info msg="retrying openshift-operators"                                                                                 │
│ E1015 13:28:14.557753       1 queueinformer_operator.go:186] Sync "openshift-operators" failed: {jaeger-product stable jaeger-operator.v1.13.1 {installed │
│ -redhat-openshift-operators openshift-operators}} not found: CatalogSource {installed-redhat-openshift-operators openshift-operators} not found
```

Actual results:

Jaeger subscription never resolves.


Expected results:

Jaeger subscription succeeds.


Additional info:

Removing and re-installing Jaeger usually solves this.

Comment 1 Alexander Greene 2019-10-15 16:59:34 UTC
Moving to 4.3 as this is not release blocking for 4.2.  We will continue to try to reproduce there and backport any applicable fixes to z-stream releases.

Comment 2 Alexander Greene 2019-10-16 13:49:54 UTC
This is not reproducible on a 4.3 cluster - but is reproducible on a 4.1.18 cluster.

Comment 3 Alexander Greene 2019-10-21 17:44:15 UTC
Moving to `ON_QA` to allow QA to verify that this does not happen on a 4.3 cluster.

Comment 4 Bruno Andrade 2019-10-23 21:49:44 UTC
Moving to VERIFIED, this issue does not happen in 4.3, Elasticsearch and Jaeger operators were installed almost instantly. CSC's are not referenced anymore from 4.2 and I did not find any issue at the Operator Source.

Cluster Version:  4.3.0-0.nightly-2019-10-23-140012
OLM version: 0.12.0
git commit: fef533c6174413418a9dc581a54a6438f45da982

Comment 6 errata-xmlrpc 2020-01-23 11:07:31 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:0062