Bug 1690592

Summary:	[marketplace] API group and version are incorrect
Product:	OpenShift Container Platform	Reporter:	Aravindh Puthiyaparambil <aravindh>
Component:	OLM	Assignee:	Aravindh Puthiyaparambil <aravindh>
Status:	CLOSED ERRATA	QA Contact:	Fan Jia <jfan>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.0	CC:	jforrest
Target Milestone:	---
Target Release:	4.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: API was marked as alpha Consequence: Released to customer with an alpha API Fix: Updated API to v1 Result: v1 APIs	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 10:46:13 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:

Description Aravindh Puthiyaparambil 2019-03-19 18:51:12 UTC

The API group and version of OperatorSource and CatalogSourceConfig are set incorrectly. The group should be "operators.openshift.io" for consistency. The version cannot be v1alpha1 for a GA feature.

Comment 1 Jessica Forrester 2019-03-19 19:04:43 UTC

Decision from Clayton is to use operators.coreos.com

Comment 2 Aravindh Puthiyaparambil 2019-03-21 01:53:51 UTC

https://github.com/operator-framework/operator-marketplace/pull/139

Comment 3 Fan Jia 2019-03-26 06:30:22 UTC

test env:
cv : 4.0.0-0.nightly-2019-03-25-180911
marketplace image:quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:c900dea42db87f2284e500d24718cd4d8fb5a4c4255ad26bccd721024b7dc91a
marketplace commit:e274d6b40505e977e12061becf27218f5eb717fb

the api group of opsrc&csc:
1)# oc get crd catalogsourceconfigs.operators.coreos.com -o yaml | grep group
  group: operators.coreos.com
2)# oc get crd operatorsources.operators.coreos.com -o yaml | grep group
  group: operators.coreos.com

Comment 5 errata-xmlrpc 2019-06-04 10:46:13 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:0758