Comment 30 for bug 1902425

I've done some more testing with 2.8.5, and I am able to deploy with Auto assign addresses if the subnets are set to unmanaged and I have a reserved range. However, once I assign a static address from the same subnet (outside the reserved ranges - the subnets are unmanaged), deploy will fail with the AUTO IP error. This happens regardless of whether I set the static IP via the GUI or via the API.

FURTHERMORE, deploy will succeed if I set EITHER of the two network interfaces to Auto assign. However, if both interfaces have static IP, then deploy will fail with the AUTO IP error. The interfaces are in different subnets (10.12.0.0/24 and 10.14.0.0/16). I tried setting the IP addresses to 10.12.0.123 and 10.14.0.123, respectively. If one or both are Auto assign, deployment succeeds. If both are set to Static assign, then deployment fails. Neither of these IP addresses have been used for anything ever in the cluster, as far as I know (I also tried with a different address for both).

So, the problem only seems to manifest on the two-interface machine IF BOTH INTERFACES ARE SET TO STATIC ASSIGN. Apparently the IP addresses and subnets are fine, as deploy will succeed if I set either interface to Auto assign. This really looks like a bug still in 2.8.5.