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

Bug 1737385

Summary:	The CRDs defined in the kubefed-operator are different with the CRDs used in kubefed
Product:	OpenShift Container Platform	Reporter:	Qin Ping <piqin>
Component:	Federation	Assignee:	Aniket Bhat <anbhat>
Status:	CLOSED ERRATA	QA Contact:	Qin Ping <piqin>
Severity:	medium	Docs Contact:
Priority:	urgent
Version:	4.2.0	CC:	anbhat
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-16 06:34:43 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 Qin Ping 2019-08-05 09:18:14 UTC

Description of problem:
The CRDs defined in the kubefed-operator are different with the CRDs used in kubefed

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

https://github.com/openshift/kubefed-operator/tree/release-4.2/deploy/olm-catalog/kubefed-operator/4.2(commit: a3101552eb78449b7afbf5ef71f233fac240e826)

quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908041300-ose-kubefed


How reproducible:
100%

Steps to Reproduce:
1. 
2.
3.

Actual results:
The CRDs created with manifests from the kubefed-operator are:
$ oc get crd|grep kubefed
clusterpropagatedversions.core.kubefed.k8s.io               2019-08-05T08:37:32Z
dnsendpoints.multiclusterdns.kubefed.k8s.io                 2019-08-05T08:37:32Z
domains.multiclusterdns.kubefed.k8s.io                      2019-08-05T08:37:32Z
federatedservicestatuses.core.kubefed.k8s.io                2019-08-05T08:37:32Z
federatedtypeconfigs.core.kubefed.k8s.io                    2019-08-05T08:37:32Z
ingressdnsrecords.multiclusterdns.kubefed.k8s.io            2019-08-05T08:37:32Z
kubefedclusters.core.kubefed.k8s.io                         2019-08-05T08:37:32Z
kubefedconfigs.core.kubefed.k8s.io                          2019-08-05T08:37:32Z
kubefeds.operator.kubefed.io                                2019-08-05T08:37:32Z
kubefedwebhooks.operator.kubefed.io                         2019-08-05T08:37:32Z
propagatedversions.core.kubefed.k8s.io                      2019-08-05T08:37:32Z
replicaschedulingpreferences.scheduling.kubefed.k8s.io      2019-08-05T08:37:32Z
servicednsrecords.multiclusterdns.kubefed.k8s.io            2019-08-05T08:37:32Z

Some crds's group is xxx.kubefed.k8s.io, some crds's group is xxx.kubefed.io, seems for the kubefed, it's using the group xxx.kubefed.io.

So, when starting kubefed controller manager, we get the following error:
F0805 09:13:42.978529       1 controller-manager.go:221] Error retrieving KubeFedConfig "federation-system/kubefed": no matches for kind "KubeFedConfig" in version "core.kubefed.io/v1beta1"

Expected results:


Additional info:

Comment 1 Qin Ping 2019-08-07 06:12:16 UTC

Verified with images:
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061459-ose-kubefed-operator
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061126-ose-kubefed

Comment 2 errata-xmlrpc 2019-10-16 06:34:43 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:2922