Created attachment 1675387 [details]
netutil daemonset spec

Description of problem:

I'm running cnv-tests on a local kubevirtci cluster using k8s-1.17 provider. A lot of networking test fails due to failure creating bridge network. I was able to narrow down the problem to failure in applying the following policy:

{'apiVersion': 'nmstate.io/v1alpha1', 'kind': 'NodeNetworkConfigurationPolicy', 'metadata': {'name': 'test-network-operator'}, 'spec': {'desiredState': {'interfaces': [{'name': 'br1test', 'type': 'linux-bridge', 'state': 'up', 'bridge': {'options': {'stp': {'enabled': False}}, 'port': []}}]}}}


How reproducible:
100%

Steps to Reproduce:
1. Start kubevirt cluster (cd kubevirtci; make cluster-up; cd cnv-tests; UPSTREAM=1 make cluster-install-hco)
2. Create netutils daemonset (kubectl create -f netutil-deamon-set.yaml, attached)
3. Create namespace (kubectl create namespace cluster-addons-operator-test-network-addons-operator)
4. Create policy (kubectl create -f node-network-config.yaml, attached)

Actual results:
Interface br1test created on node01 but not on node02.

Expected results:
Interface br1test created on node01 and node02.

Additional info:

$ export | grep KUBE
declare -x KUBEVIRT_NUM_NODES="2"
declare -x KUBEVIRT_NUM_SECONDARY_NICS="1"
declare -x KUBEVIRT_PROVIDER="k8s-1.17"