CNI loading failure causing spiderIPpool ip exhaustion

[jiayi-1994]

Spiderpool Version

v0.9.7

Main CNI

macvlan

bug description

In the case of multiple NICs, if NIC 1 succeeds in assigning an ip from sp1, and NIC 2 fails to assign an ip (maybe sp2 has run out of ip), it will result in a creation failure and cause sp1 to run out of ip as well.

The multus call to cni ADD fails with a DEL rollback, but the SpiderPool is skipped, resulting in an entire SpiderIpool being exhausted.

What did you expect to happen?

how to fix it Or use subnet instead ?

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

No response

Additional Context

No response

[ty-dc]

Thanks for your feedback, do you have some spiderpool-controller and agent logs to provide? Also kubectl describe po to show the specific error?