requestPoolHelper can loop forever if IPAM plugin lets it

[bboreham]

If I read it correctly, the expectation is that if FindAvailableNetwork indicates an overlap then requestPoolHelper can request another pool and the plugin will either return a different one or fail.

I have a plugin that does neither: it returns the same pool every time, because it is acting as glue to some pre-existing technology. Both Docker and the plugin spin rapidly, with Docker using a lot of CPU.

I think I can avoid getting into this situation by changing the way my plugin is called, but I might suggest putting a counter in requestPoolHelper to break the loop after some limit and tell the user what happened.

[GordonTheTurtle]

@bboreham It has been detected that this issue has not received any activity in over 6 months. Can you please let us know if it is still relevant:

• For a bug: do you still experience the issue with the latest version?
• For a feature request: was your request appropriately answered in a later version?

Thank you!
This issue will be automatically closed in 1 week unless it is commented on.
For more information please refer to #1926