Description of problem: Third-party network operators need to set the Network.config.openshift.io/Status field, but the cluster-network-operator overwrites it with blanks! Version-Release number of selected component (if applicable): 4.1.0 Fix: Don't write any network status if we're not installing a network.
This blocks third-party network operators. We'll probably have to backport this to 4.1.
https://github.com/openshift/cluster-network-operator/pull/173 merged
Verified this bug on 4.2.0-0.nightly-2019-06-25-222454 When setup cluster with 'networkType: OpenShiftSDN_bak'. the status of operator.config is nil [root@preserve-zzhao 0620]# oc get networks.operator.openshift.io -o yaml apiVersion: v1 items: - apiVersion: operator.openshift.io/v1 kind: Network metadata: creationTimestamp: "2019-06-26T08:40:00Z" generation: 1 name: cluster resourceVersion: "1293" selfLink: /apis/operator.openshift.io/v1/networks/cluster uid: fc2fbd5c-97ed-11e9-ac0d-068d4029efe2 spec: clusterNetwork: - cidr: 10.128.0.0/14 hostPrefix: 23 defaultNetwork: type: OpenShiftSDN_bak serviceNetwork: - 172.30.0.0/16 status: {} kind: List metadata: resourceVersion: "" selfLink: "" [root@preserve-zzhao 0620]# oc get co network NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE network 4.2.0-0.nightly-2019-06-25-222454 True False False 10m
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