Comment 4 for bug 1509077

This needs to be fixed with a data migration because we cannot update the subnet in _claim_auto_ip because there will be not IP address assigned yet. Without having the IP address that should be assigned we don't know what subnet this interface should be connected to.

We could use the nodegroup that the node is connected to, but that will be removed in 2.0 which will cause that simple fix to break as well. The best thing to do is make sure that the subnet is linked in a data migration on upgrade.