Bug 1722759

Summary: kubefedconfig.spec.featureGates is null when installing kubefed control plane with kubefed-operator
Product: OpenShift Container Platform Reporter: Qin Ping <piqin>
Component: FederationAssignee: Paul Morie <pmorie>
Status: CLOSED ERRATA QA Contact: Qin Ping <piqin>
Severity: low Docs Contact:
Priority: high    
Version: 4.2.0CC: mnewby
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:32:19 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-06-21 08:21:02 UTC 
Description of problem:
kubefedconfig.spec.featureGates is null when installing kubefed control plane with kubefed-operator


Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME      VERSION                             AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.2.0-0.nightly-2019-06-19-210910   True        False         3h52m   Cluster version is 4.2.0-0.nightly-2019-06-19-210910

kubefed-operator: branch release-4.2(10f2d7f25bbbb9d81406931576da3c2bb4fe2e98)

How reproducible:
100%

Steps to Reproduce:
1.Install operator with cmd: ./scripts/install-kubefed.sh -n federation-test -d cluster
2. Check kubefedconfig object
3.

Actual results:
$ oc get kubefedconfig kubefed -n federation-test -ojson|jq .spec.featureGates
[]

Expected results:
https://github.com/kubernetes-sigs/kubefed/blob/master/config/kubefedconfig.yaml

Additional info:
$ oc get kubefed kubefed-resource -n federation-test -ojson
{
    "apiVersion": "operator.kubefed.io/v1alpha1",
    "kind": "KubeFed",
    "metadata": {
        "annotations": {
            "kubectl.kubernetes.io/last-applied-configuration": "{\"apiVersion\":\"operator.kubefed.io/v1alpha1\",\"kind\":\"KubeFed\",\"metadata\":{\"annotations\":{},\"name\":\"kubefed-resource\",\"namespace\":\"federation-test\"},\"spec\":{\"scope\":\"Namespaced\"}}\n"
        },
        "creationTimestamp": "2019-06-21T08:17:33Z",
        "generation": 1,
        "name": "kubefed-resource",
        "namespace": "federation-test",
        "resourceVersion": "72526",
        "selfLink": "/apis/operator.kubefed.io/v1alpha1/namespaces/federation-test/kubefeds/kubefed-resource",
        "uid": "053d0b09-93fd-11e9-b336-069d557c2d62"
    },
    "spec": {
        "scope": "Namespaced"
    },
    "status": {
        "version": "0.1.0"
    }
}
Comment 1 Maru Newby 2019-07-23 18:02:19 UTC 
This should be fixed upstream by https://github.com/kubernetes-sigs/kubefed/pull/1015 and https://github.com/kubernetes-sigs/kubefed/pull/941, and these fixes have been released as of rc3.
Comment 2 Qin Ping 2019-08-07 08:07:44 UTC 
verified with images:
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061126-ose-kubefed
quay.io/openshift-release-dev/ocp-v4.0-art-dev:v4.2.0-201908061459-ose-kubefed-operator

$ oc get kubefedconfig kubefed -ojson|jq .spec.featureGates
[
  {
    "configuration": "Enabled",
    "name": "CrossClusterServiceDiscovery"
  },
  {
    "configuration": "Enabled",
    "name": "FederatedIngress"
  },
  {
    "configuration": "Enabled",
    "name": "PushReconciler"
  },
  {
    "configuration": "Enabled",
    "name": "SchedulerPreferences"
  }
]
Comment 3 errata-xmlrpc 2019-10-16 06:32:19 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