Bug 1906895 - Elasticsearch Operator 4.7 csv missing wording for ECK and does not have 5.0 csv
Summary: Elasticsearch Operator 4.7 csv missing wording for ECK and does not have 5.0 csv
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.7
Hardware: Unspecified
OS: Unspecified
high
low
Target Milestone: ---
: 4.7.0
Assignee: Periklis Tsirakidis
QA Contact: Anping Li
URL:
Whiteboard: logging-exploration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-11 17:30 UTC by ewolinet
Modified: 2021-02-24 11:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-02-24 11:22:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift elasticsearch-operator pull 597 0 None closed Bug 1906895: Fixing lost changes in 4.7 csv and adding 5.0 csv for disconnecting from ART 2021-02-08 09:59:37 UTC
Github openshift elasticsearch-operator pull 601 0 None closed Bug 1906895: Remove replace directive in 5.0 CSV manifest 2021-02-08 09:59:36 UTC
Red Hat Product Errata RHBA-2021:0652 0 None None None 2021-02-24 11:23:16 UTC

Description ewolinet 2020-12-11 17:30:09 UTC
Description of problem:
Elasticsearch Operator 4.7 csv is missing wording to use the elastic.co eck operator for a general purpose elasticsearch operator.

Also, EO is missing a 5.0 manifest directory so that it can create 5.0 artifacts with CPaaS.


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

How reproducible:
Always

Comment 2 Anping Li 2020-12-16 07:13:04 UTC
#opm index add --bundles registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-elasticsearch-operator-bundle@sha256:41615c963dd7a55ba4eba06ec204e25c10913af0adc8b37f887d13db8b1fbb1b --from-index  registry-proxy.engineering.redhat.com/rh-osbs/iib-pub-pending:v4.7  --tag example.com/index/iib:latest -c docker

INFO[0106] Could not find optional dependencies file     dir=bundle_tmp992968836 file=bundle_tmp992968836/metadata load=annotations
INFO[0106] found csv, loading bundle                     dir=bundle_tmp992968836 file=bundle_tmp992968836/manifests load=bundle
INFO[0106] loading bundle file                           dir=bundle_tmp992968836/manifests file=elasticsearch-operator.v5.0.0.clusterserviceversion.yaml load=bundle
INFO[0106] loading bundle file                           dir=bundle_tmp992968836/manifests file=logging.openshift.io_elasticsearches_crd.yaml load=bundle
INFO[0106] loading bundle file                           dir=bundle_tmp992968836/manifests file=logging.openshift.io_kibanas_crd.yaml load=bundle
ERRO[0106] permissive mode disabled                      bundles="[registry-proxy.engineering.redhat.com/rh-osbs/openshift-ose-elasticsearch-operator-bundle@sha256:41615c963dd7a55ba4eba06ec204e25c10913af0adc8b37f887d13db8b1fbb1b]" error="error loading bundle from image: Invalid bundle elasticsearch-operator.5.0-6, bundle specifies a non-existent replacement elasticsearch-operator.v4.7.0"
Error: error loading bundle from image: Invalid bundle elasticsearch-operator.5.0-6, bundle specifies a non-existent replacement elasticsearch-operator.v4.7.0

Comment 4 Anping Li 2020-12-18 10:34:08 UTC
Same error when using the latest elasticsearch-operator-bundle-container-v5.0.6-6. As there isn't a commit id in the image, I couldn't know if this image include the fix.

Comment 6 Anping Li 2020-12-21 03:00:53 UTC
Verified on elasticsearch-operator-bundle-container-v5.0.8-2

Comment 10 errata-xmlrpc 2021-02-24 11:22:30 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 (Errata Advisory for Openshift Logging 5.0.0), 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-2021:0652


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