Bug 1786218

A bit more information on this may be helpful. Any error/logs on the kuryr-controller? Any erros on the kuryr-cni on the worker ostest-xlw6j-worker-8mttb? What is this test doing?

I can see some logs from kuryr-cni
2019-12-25 08:25:45.383 56 ERROR kuryr_kubernetes.cni.daemon.service [-] Error when processing addNetwork request. CNI Params: {'CNI_IFNAME': 'eth0', 'CNI_NETNS': '/proc/1392981/ns/net', 'CNI_PATH': '/opt/multus/bin:/var/lib/cni/bin', 'CNI_COMMAND': 'ADD', 'CNI_CONTAINERID': '531d21b76015f7afc46e2641d30c00354f89ed534ea326cbb75b4aae8aeb9be3', 'CNI_ARGS': 'IgnoreUnknown=true;K8S_POD_NAMESPACE=storage;K8S_POD_NAME=iscsi-target;K8S_POD_INFRA_CONTAINER_ID=531d21b76015f7afc46e2641d30c00354f89ed534ea326cbb75b4aae8aeb9be3'}: pyroute2.netlink.exceptions.NetlinkError: (17, 'File exists')

Ohh, ok, then this is most probably a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1786298.

Closing it as duplicate of the other one, please reopen if hit it again with newer versions. That is already fixed

*** This bug has been marked as a duplicate of bug 1786298 ***

Iscsi function is passed on osp13 with kuryr enabled.
cluster version is 4.3.0-0.nightly-2020-01-06-185654
1.Create iscsi target
2.Config iscsi initiator
3.Create pv, pvc, pod
4.Pod is running
pod/iscsi   1/1     Running   0          5h25m
Name:         iscsi
Namespace:    default
Priority:     0
Node:         ostest-vqq5d-worker-6jcw4/10.196.0.14
Start Time:   Tue, 07 Jan 2020 22:17:21 -0500
Labels:       name=iscsi
Annotations:  k8s.v1.cni.cncf.io/networks-status:
                [{
                    "name": "kuryr",
                    "interface": "eth0",
                    "ips": [
                        "10.128.82.3"
                    ],
                    "mac": "fa:16:3e:a6:94:3d",
                    "dns": {}
                }]
              openstack.org/kuryr-pod-label: {"name": "iscsi"}
              openstack.org/kuryr-vif:
                {"versioned_object.changes": ["default_vif"], "versioned_object.data": {"additional_vifs": {}, "default_vif": {"versioned_object.changes":...
Status:       Running
IP:           10.128.82.3
IPs:
  IP:  10.128.82.3
Containers:
  iscsi:
    Container ID:   cri-o://9b8c2189b1b3c0aa985fe971f719d0825f9ec69b4f37f96c0ddcae1496e777af
    Image:          jhou/hello-openshift
    Image ID:       docker.io/jhou/hello-openshift@sha256:72a676ac8fe20f2506502d128b021a64f92d00bf444c64e000121b36011655aa
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Tue, 07 Jan 2020 22:18:00 -0500
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /mnt/iscsi from iscsi (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-rxfcf (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  iscsi:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  pvc-iscsi
    ReadOnly:   false
  default-token-rxfcf:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-rxfcf
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:          <none>

Update to verified since iscsi function works on osp with kuryr enabled env. 
Issue "NetlinkError: (17, 'File exists')" is tacking by https://bugzilla.redhat.com/show_bug.cgi?id=1786298

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-2020:2436