Cooperating with kube ovn may result in the inability to start after restarting

[niezhicheng]

[root@master ~]# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
default nfs-subdir-external-provisioner-5bb5d5cf4b-z5zvb 0/1 Error 8 102d
kube-system coredns-6d8c4cb4d-slcj7 0/1 Error 9 102d
kube-system coredns-6d8c4cb4d-thqb9 0/1 Error 9 102d
kube-system etcd-master 1/1 Running 11 (43m ago) 102d
kube-system kube-apiserver-master 1/1 Running 11 (43m ago) 102d
kube-system kube-controller-manager-master 1/1 Running 12 (43m ago) 102d
kube-system kube-multus-ds-lnbx7 0/1 Init:CrashLoopBackOff 13 (48s ago) 26d
kube-system kube-ovn-cni-vfnbw 1/1 Running 12 (43m ago) 102d
kube-system kube-ovn-controller-564488f795-6crj8 1/1 Running 14 (43m ago) 102d
kube-system kube-ovn-monitor-c6c969499-cm4gx 1/1 Running 13 (43m ago) 102d
kube-system kube-ovn-pinger-mrlq6 0/1 Error 11 102d
kube-system kube-proxy-4g4cv 1/1 Running 11 (43m ago) 102d
kube-system kube-scheduler-master 1/1 Running 12 (43m ago) 102d
kube-system ovn-central-5bccdfcd7d-xhs2k 1/1 Running 11 (43m ago) 102d
kube-system ovs-ovn-ldc29 1/1 Running 11 (43m ago) 102d
kube-system vpc-nat-gw-vpc1-subnet1-gateway-0 0/1 Error 3 26d

What happend:

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Multus version
  image path and image ID (from 'docker images')
• Kubernetes version (use kubectl version): 1.23.1
• Primary CNI for Kubernetes cluster:
• OS (e.g. from /etc/os-release):
• [root@master ~]# cat /etc/os-release
  NAME="CentOS Linux"
  VERSION="7 (Core)"
  ID="centos"
  ID_LIKE="rhel fedora"
  VERSION_ID="7"
  PRETTY_NAME="CentOS Linux 7 (Core)"
  ANSI_COLOR="0;31"
  CPE_NAME="cpe:/o:centos:centos:7"
  HOME_URL="https://www.centos.org/"
  BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

• File of '/etc/cni/net.d/'
• File of '/etc/cni/multus/net.d'
• NetworkAttachment info (use kubectl get net-attach-def -o yaml)
• Target pod yaml info (with annotation, use kubectl get pod <podname> -o yaml)
• Other log outputs (if you use multus logging)