+++ This bug was initially created as a clone of Bug #1761871 +++ 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. --- Additional comment from Alexander Greene on 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. --- Additional comment from Alexander Greene on 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. --- Additional comment from Alexander Greene on 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.
Hi, I couldn't reproduce this issue on 4.2.0-0.nightly-2019-11-06-011942 (4.2.2) as ElasticSearch Operator got installed without a few minutes. This bug is no longer an issue. Thanks, Vu
Could not reproduce this issue on 4.2.0-0.nightly-2019-11-13-013411, so marking as VERIFIED
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-2019:3869