Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1685459 - [marketplace]The operator "elasticsearch-operator" is downloaded from Community Operator as "elasticserach-operator" cause the operator can't be added to the CSC
Summary: [marketplace]The operator "elasticsearch-operator" is downloaded from Communi...
Keywords:
Status: VERIFIED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: OLM
Version: 4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: ---
Assignee: Sami Shahin
QA Contact: Fan Jia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-05 09:45 UTC by Fan Jia
Modified: 2019-03-12 14:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:


Attachments (Terms of Use)

Description Fan Jia 2019-03-05 09:45:29 UTC
Description of problem:
The operator `elasticsearch-operator` comes from "pre-install" operatorsource community-operator can't be added to the csc when install it from the Operator Hub UI because it is stored as `elasticserach-operator`

Version-Release number of selected component (if applicable):
clusterversion:4.0.0-0.nightly-2019-03-04-234414
console  image:  quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:af4309742b18e8e0e4dc2c7f96c044ede1f2d40c325a9462a25398c39c67bd9f

How reproducible:
always

Steps to Reproduce:
1.choose "elasticsearch-operator" operator in the basic operator hub UI,and click install 
2.click "subscription" button in the loaded subscription page

Actual results:
1.after step 2, the default csc "installed-community-openshift-operators" check the "elasticsearch-operator" is an unlegal operator and the csc can't be updated successfully
#oc get csc 
NAME                                      TARGETNAMESPACE         PACKAGES            STATUS        DISPLAYNAME           PUBLISHER   MESSAGE                                                                                           AGE
installed-community-openshift-operators   openshift-operators     elasticsearch-operator   Configuring   Community Operators   Community   
Still resolving package(s) - elasticsearch-operator. Please make sure these are valid packages.   106m

2. can get the packagemanifest `elasticsearch-operator`
1) #oc get pcakagemanifests | grep "elasticsearch-operator"
elasticsearch-operator   3h

2) #oc describe packagemanifest elasticsearch-operator 
Name:         elasticsearch-operator
Namespace:    openshift-marketplace
Labels:       catalog=community-operators
              catalog-namespace=openshift-marketplace
              csc-owner-name=community-operators
              csc-owner-namespace=openshift-marketplace
              olm-visibility=hidden
              openshift-marketplace=true
              opsrc-datastore=true
              opsrc-owner-name=community-operators
              opsrc-owner-namespace=openshift-marketplace
              opsrc-provider=community
              provider=Red Hat, Inc.
              provider-url=
...
  Default Channel:  preview
  Package Name:     elasticsearch-operator
  Provider:
    Name:  Red Hat, Inc
Events:    <none>

3. the package is downloaded as "elasticserach-operator" in csc "community-operators"
the logs of community-operators
`
time="2019-03-05T06:12:47Z" level=info msg="package(s) specified are - descheduler,automationbroker,templateservicebroker,elasticserach-operator,etcd,prometheus,percona,planetscale,strimzi-kafka-operator,svt-app-operator,federation,jaeger,cluster-logging,oneagent,kiecloud-operator,metering,camel-k,node-problem-detector,postgresql" port=50051 type=appregistry
time="2019-03-05T06:12:47Z" level=info msg="input sanitized - sources: [openshift-marketplace/community-operators], packages: [descheduler automationbroker templateservicebroker elasticserach-operator etcd prometheus percona planetscale strimzi-kafka-operator svt-app-operator federation jaeger cluster-logging oneagent kiecloud-operator metering camel-k node-problem-detector postgresql]" port=50051 type=appregistry
time="2019-03-05T06:12:48Z" level=info msg="resolved the following packages: [community-operators/elasticserach-operator:0.0.1 community-operators/prometheus:0.22.3 community-operators/strimzi-kafka-operator:0.0.2 community-operators/cluster-logging:0.0.4 community-operators/templateservicebroker:0.2.0 community-operators/federation:0.0.1 community-operators/etcd:0.0.5 community-operators/jaeger:0.0.5 community-operators/automationbroker:0.2.2 community-operators/percona:0.0.3 community-operators/planetscale:0.0.2 community-operators/postgresql:0.0.1 community-operators/metering:0.13.2 community-operators/descheduler:0.0.2 community-operators/node-problem-detector:0.0.1 community-operators/kiecloud-operator:0.0.1 community-operators/svt-app-operator:0.0.1 community-operators/camel-k:0.2.0 community-operators/oneagent:0.0.3]" port=50051 type=appregistry
time="2019-03-05T06:12:48Z" level=info msg="downloading repository: community-operators/elasticserach-operator:0.0.1 from https://quay.io/cnr" port=50051 type=appregistry
`

Expected results:
1.after step 2, the default csc  "installed-community-openshift-operators" check the  "elasticsearch-operator" is a legal operator and the csc can be  updated successfully

Additional info:

Comment 1 Sami Shahin 2019-03-05 16:18:15 UTC
The image I pushed to quay last night had a typo in the operator name. The correct name is `elasticsearch-operator` while the bundle was pushed as `elasticserach-operator`. I have since updated the repo name to match the operator's package, and this issue should be resolved.

Comment 2 Fan Jia 2019-03-06 05:11:05 UTC
The name of "elasticsearch-operator" has been right now. The issue won't appear again. This operator can be installed now.
test env:
clusterversion:4.0.0-0.nightly-2019-03-04-234414


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