I think this is a known issue in 2.0.x where, under certain conditions, some IPs are still marked in use. It seems to be triggered by instance not starting properly (but not only).
I think this is a known issue in 2.0.x where, under certain conditions, some IPs are still marked in use. It seems to be triggered by instance not starting properly (but not only).