1678644 – [marketplace] Install operator failed (catalogsource not found)

Bug 1678644 - [marketplace] Install operator failed (catalogsource not found)

Summary: [marketplace] Install operator failed (catalogsource not found)

Keywords:
Status:	CLOSED DUPLICATE of bug 1679309
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	OLM
Sub Component:
Version:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	urgent
Severity:	urgent
Target Milestone:	---
Target Release:	4.1.0
Assignee:	Aravindh Puthiyaparambil
QA Contact:	Fan Jia
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2019-02-19 10:01 UTC by Fan Jia
Modified:	2019-03-12 14:26 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2019-02-20 22:51:31 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Fan Jia 2019-02-19 10:01:46 UTC

Description of problem:
Install operator failed through the Operatorhub UI. The catalogoperator logs the `installed-XXXX  catalogsource` not found. No csv found in the openshift-operators.

Version-Release number of selected component (if applicable):
1.clusterversion:4.0.0-0.nightly-2019-02-18-224151
2.marketplace image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fa1bfe505ba77054fd42aa8d2af7094dbe3a19242639e18b6924b564f583799a
3.olm : quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:a8ca6bf86ff96fc7487ed4d80b7d8f9fa51c6a0fbc3b6ec95b3e73ea2f7fdf2a

How reproducible:
always

Steps to Reproduce:
1.install operator “federationv2” to OG “global-operators” through the Operatorhub UI

Actual results:
1.no csv file in ns openshif-operators

catalog logs:
`E0219 09:17:35.341458       1 queueinformer_operator.go:155] Sync "openshift-operators" failed: {federationv2 alpha federationv2.v0.0.2 {installed-community-global-operators openshift-operators}} not found: rpc error: code = Unknown desc = no bundle found for csv federationv2.v0.0.2`


Expected results:
1.there is csv about "federationv2" in ns openshift-operators and the operator is installed successfully

Additional info:
the resource situation in the cluster
1.#oc get catalogsource -n openshift-operators
NAME                                   NAME                  TYPE      PUBLISHER   AGE
installed-community-global-operators   Community Operators   grpc      Community   159m
2.#oc get pods -n openshift-operators
No resources found.
3.#oc get csv -n openshift-operators
No resources found.
4.#oc get subscription -n openshift-operators
NAME                 PACKAGE              SOURCE                                 CHANNEL
federationv2         federationv2         installed-community-global-operators   alpha
5.#oc get pods -n openshift-marketplace
NAME                                                    READY     STATUS    RESTARTS   AGE
installed-community-global-operators-646f8b54f-n5qtv    1/1       Running   0          161m
marketplace-operator-cc848865c-gslpc                    1/1       Running   0          75s

Comment 1 Aravindh Puthiyaparambil 2019-02-19 14:46:40 UTC

What logs did you see in the marketplace-operator in this situation?

Comment 2 Aravindh Puthiyaparambil 2019-02-19 18:50:28 UTC

This might be related to https://bugzilla.redhat.com/show_bug.cgi?id=1677329. If 1677329 happens then is very likely that this bug will occur too.

Comment 3 Aravindh Puthiyaparambil 2019-02-19 19:17:40 UTC

I retract my previous comment (https://bugzilla.redhat.com/show_bug.cgi?id=1678644#c2). This is NOT related to https://bugzilla.redhat.com/show_bug.cgi?id=1677329.

Given that you are seeing the federationv2 subscription as follows:
4.#oc get subscription -n openshift-operators
NAME                 PACKAGE              SOURCE                                 CHANNEL
federationv2         federationv2         installed-community-global-operators   alpha

It looks like Marketplace handled this request. However for some reason the federationv2 Subscription did not get acted upon. What does "oc get installplans -n openshift-operators -o yaml" show?

Please run this issue by the OLM QE also.

Comment 4 Fan Jia 2019-02-20 05:47:58 UTC

(In reply to aravindh from comment #1)
> What logs did you see in the marketplace-operator in this situation?
marketplace's log
`
time="2019-02-20T05:28:25Z" level=info msg="Reconciling CatalogSourceConfig openshift-marketplace/installed-community-global-operators\n"
time="2019-02-20T05:28:25Z" level=info msg="Scheduling for configuring" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:25Z" level=info msg="Reconciling CatalogSourceConfig openshift-marketplace/installed-community-global-operators\n"
time="2019-02-20T05:28:25Z" level=info msg="Created ServiceAccount installed-community-global-operators" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="Created Role installed-community-global-operators" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="Created RoleBinding installed-community-global-operators" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="Created Deployment installed-community-global-operators with registry command: [appregistry-server -s openshift-marketplace/community-operators -o federationv2]" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="Created Service installed-community-global-operators" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="Creating CatalogSource installed-community-global-operators" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="Created CatalogSource installed-community-global-operators" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="The object has been successfully reconciled" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig
time="2019-02-20T05:28:26Z" level=info msg="Reconciling CatalogSourceConfig openshift-marketplace/installed-community-global-operators\n"
time="2019-02-20T05:28:26Z" level=info msg="No action taken, the object has already been reconciled" name=installed-community-global-operators targetNamespace=openshift-operators type=CatalogSourceConfig

`
(In reply to aravindh from comment #3)
> installplans -n openshift-operators -o yaml" show?

#oc get installplans -n openshift-operators -o yaml
apiVersion: v1
items: []
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Comment 5 Fan Jia 2019-02-20 09:20:54 UTC

new test env
clusterversion : `4.0.0-0.nightly-2019-02-19-205011`
catalog logs:
`E0220 08:57:23.118568       1 queueinformer_operator.go:155] Sync "openshift-operators" failed: {federationv2 alpha federationv2.v0.0.2 {installed-community-global-operators openshift-operators}} not found: CatalogSource {installed-community-global-operators openshift-operators} not found`

the error only show once and the operator can be installed success at last. 
(a little difference between the errors as this one doesn't have the `: rpc error: code = Unknown desc = no bundle found for csv federationv2.v0.0.2`)

Comment 6 Aravindh Puthiyaparambil 2019-02-20 17:43:55 UTC

(In reply to Fan Jia from comment #4)
> (In reply to aravindh from comment #1)
> > What logs did you see in the marketplace-operator in this situation?
> marketplace's log
> `
> time="2019-02-20T05:28:25Z" level=info msg="Reconciling CatalogSourceConfig
> openshift-marketplace/installed-community-global-operators\n"
> time="2019-02-20T05:28:25Z" level=info msg="Scheduling for configuring"
> name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:25Z" level=info msg="Reconciling CatalogSourceConfig
> openshift-marketplace/installed-community-global-operators\n"
> time="2019-02-20T05:28:25Z" level=info msg="Created ServiceAccount
> installed-community-global-operators"
> name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="Created Role
> installed-community-global-operators"
> name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="Created RoleBinding
> installed-community-global-operators"
> name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="Created Deployment
> installed-community-global-operators with registry command:
> [appregistry-server -s openshift-marketplace/community-operators -o
> federationv2]" name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="Created Service
> installed-community-global-operators"
> name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="Creating CatalogSource
> installed-community-global-operators"
> name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="Created CatalogSource
> installed-community-global-operators"
> name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="The object has been successfully
> reconciled" name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> time="2019-02-20T05:28:26Z" level=info msg="Reconciling CatalogSourceConfig
> openshift-marketplace/installed-community-global-operators\n"
> time="2019-02-20T05:28:26Z" level=info msg="No action taken, the object has
> already been reconciled" name=installed-community-global-operators
> targetNamespace=openshift-operators type=CatalogSourceConfig
> 

The above log confirms that the marketplace operator handled the request successfully.

> `
> (In reply to aravindh from comment #3)
> > installplans -n openshift-operators -o yaml" show?
> 
> #oc get installplans -n openshift-operators -o yaml
> apiVersion: v1
> items: []
> kind: List
> metadata:
>   resourceVersion: ""
>   selfLink: ""

So it looks like the Subscription did not get picked up. Unfortunately this could be due to some required OLM resource being deleted as we have been seeing in many bugs. I am afraid until we get to the bottom of that issue, it will be difficult to debug this.

Comment 7 Aravindh Puthiyaparambil 2019-02-20 22:51:31 UTC


*** This bug has been marked as a duplicate of bug 1679309 ***

Note You need to log in before you can comment on or make changes to this bug.