Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1718731

Summary:	Can't create csv elasticsearch-operator.v4.1.1 because of "spec.customresourcedefinitions.owned.specDescriptors.description in body is required"
Product:	OpenShift Container Platform	Reporter:	Qiaoling Tang <qitang>
Component:	Logging	Assignee:	Jeff Cantrill <jcantril>
Status:	CLOSED ERRATA	QA Contact:	Anping Li <anli>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	4.1.z	CC:	aos-bugs, bparees, lmeyer, rmeggins, sponnaga, wking
Target Milestone:	---	Keywords:	Regression
Target Release:	4.1.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	4.1.2
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-26 08:50:23 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Qiaoling Tang 2019-06-10 08:39:55 UTC

The elasticsearch-operator couldn't be created if the elasticsearch-operator csv can't be created, the elasticsearch pods couldn't be created either, the whole logging stack can't work.

Workaround: 
1. add some words in the description part in https://github.com/openshift/elasticsearch-operator/blob/release-4.1/manifests/4.1/elasticsearch-operator.v4.1.0.clusterserviceversion.yaml#L220 and https://github.com/openshift/elasticsearch-operator/blob/release-4.1/manifests/4.1/elasticsearch-operator.v4.1.0.clusterserviceversion.yaml#L223
2. push it to a quay.io registry
3. create operator source to use this registry

Comment 2 Ben Parees 2019-06-10 18:57:28 UTC

https://github.com/openshift/elasticsearch-operator/pull/154

Comment 7 errata-xmlrpc 2019-06-26 08:50:23 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, 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:1589