Comment 28 for bug 1902425

For me this issue started happening going from 2.8.2 to 2.8.4.

I reproduced the issue in 2.8.4. once I updated to 2.9.2 the error went away.

For the people still hitting this in 2.9.2, I wonder if there is a device using an ip on the subnet? If you enable auto discovery, maybe it will discover the device? I'm not sure of an easier way to find out if there is an ip maas is getting stuck on.