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):
console image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:af4309742b18e8e0e4dc2c7f96c044ede1f2d40c325a9462a25398c39c67bd9f
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
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"
2) #oc describe packagemanifest elasticsearch-operator
provider=Red Hat, Inc.
Default Channel: preview
Package Name: elasticsearch-operator
Name: Red Hat, Inc
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
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
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.
The name of "elasticsearch-operator" has been right now. The issue won't appear again. This operator can be installed now.
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.