Describe the bug
Right now, Dynamic-network-controller will request multus and use the result to update pod network status in pod annotation k8s.v1.cni.cncf.io/network-status(details in SetNetworkStatus). When update NetworkStatus failed dynamic-network-controller just requeue the pod.
While CNI have already handle addNetworks request and add interface in the pod before SetNetworkStatus.
When the pod requeue and rehandle. Dynamic-network-controller will do addNetworks again according to k8s.v1.cni.cncf.io/network-status on pod. While this request will always failed because interface has create in pod in the initial request. and stuck all dynamic network request for this pod.

Expected behavior
SetNetworkStatus failed dosen't stuck dynamic network request for this pod.

To Reproduce
Steps to reproduce the behavior:
1.
2.
3.

Environment:

• multus-dynamic-networks-controller version: N/A
• Kubernetes version (use kubectl version): N/A
• Network-attachment-definition: N/A
• OS (e.g. from /etc/os-release): N/A
• Controller configuration (criSocketPath / multusSocketPath): N/A
• Kernel (e.g. uname -a): N/A
• Others: N/A

Additional info / context
Add any other information / context about the problem here.