This means that you can wind up with working addresses on random networks, run out of leases on the discovery range, or have your traffic go through the wrong interface die to ARP roulette. Either way, Hilarity can ensue. The Principle of Least Surprise would dictate that someone ignorantly attaching an interface that should not be configured should not do horrible things to your networking, so interfaces that are not configured should not have DHCP enabled on them.
I believe this only applies in cases where network isolation is not used.
(credit to Dan Sneddon ^^ )
Dan, is this still an issue? If not, could you please close this bug.
I thought this issue had been fixed, we modified the deployment scripts to delete the udev rule after os-net-config runs. I need to triage BZ # 1382653 however, to figure out if some version of this bug has resurfaced before closing it.
Let us close this bug as a duplicate. I think DHCP'ing all interfaces is an explicit design choice we made. *** This bug has been marked as a duplicate of bug 1382653 ***