microk8s kube-ovn addon - ovn pinger and ovn cni containers in crashloopbackoff

[parshva-shah-dsw]

Expected Behavior

All pods should get deployed

Actual Behavior

ovn controller pod logs :-

6 subnet.go:318] format subnet ovn-default, changed false
W0526 11:23:02.624182 6 warnings.go:70] unknown field "status.availableIPs"
W0526 11:23:02.624198 6 warnings.go:70] unknown field "status.usingIPs"
W0526 11:23:02.637754 6 warnings.go:70] unknown field "status.availableIPs"
W0526 11:23:02.637776 6 warnings.go:70] unknown field "status.usingIPs"
E0526 11:23:02.638029 6 subnet.go:603] subnet ovn-default cidr 10.1.0.0/16 conflict with node v2-master address 10.1.0.17
I0526 11:23:02.638274 6 event.go:285] Event(v1.ObjectReference{Kind:"Subnet", Namespace:"", Name:"ovn-default", UID:"b8ecb6a7-c449-4706-9711-1ab7c3a33fa2", APIVersion:"kubeovn.io/v1", ResourceVersion:"155805", FieldPath:""}): type: 'Warning' reason: 'ValidateLogicalSwitchFailed' subnet ovn-default cidr 10.1.0.0/16 conflict with node v2-master address 10.1.0.17
W0526 11:23:02.651569 6 warnings.go:70] unknown field "status.availableIPs"
W0526 11:23:02.651588 6 warnings.go:70] unknown field "status.usingIPs"
E0526 11:23:02.651810 6 subnet.go:186] error syncing 'ovn-default': subnet ovn-default cidr 10.1.0.0/16 conflict with node v2-master address 10.1.0.17, requeuing

Additional Info

• Kubernetes version: v1.26.4 - MicroK8s v1.26.4 revision 5219
• kube-ovn version: v1.10.0
• operation-system/kernel version: Red Hat Enterprise Linux 8.8 (Ootpa)

We are installing kube-ovn add on in microk8s in RHEL 8.8.
Below steps were used to enable add on in microk8s https://microk8s.io/docs/addon-kube-ovn
Please help here if anyone have faced same kind of issues while installing.

[evilnick]

This repository is for the microK8s.io website. If you are still experiencing an issue with microK8s, please file an issue in the
microk8s repository