Drew Erny 89edb68e89 Fix possible overlapping IPs ... A node is no longer using its load balancer IP address when it no longer has tasks that use the network that requires that load balancer. When this occurs, the swarmkit manager will free that IP in IPAM, and may reaassign it. When a task shuts down cleanly, it attempts removal of the networks it uses, and if it is the last task using those networks, this removal succeeds, and the load balancer IP is freed. However, this behavior is absent if the container fails. Removal of the networks is never attempted. To address this issue, I amend the executor. Whenever a node load balancer IP is removed or changed, that information is passedd to the executor by way of the Configure method. By keeping track of the set of node NetworkAttachments from the previous call to Configure, we can determine which, if any, have been removed or changed. At first, this seems to create a race, by which a task can be attempting to start and the network is removed right out from under it. However, this is already addressed in the controller. The controller will attempt to recreate missing networks before starting a task. Signed-off-by: Drew Erny <derny@mirantis.com> (cherry picked from commit 0d9b0ed678) Signed-off-by: Ameya Gawde <agawde@mirantis.com>		2021-06-18 10:13:59 -07:00
..
container	Fix possible overlapping IPs	2021-06-18 10:13:59 -07:00
backend.go	Remove SystemInfo() error handling.	2019-08-29 07:44:39 +08:00