Comment 3 for bug 1612293

While I understand where you're coming from I think MAAS users shouldn't really care *where* the bug is. It manifests itself in something that's not in line with the MAAS config. If in MAAS I don't have eth0 configured then it should NOT be configured, no matter what.

The MAAS source images are produced by you guys, right? If so, you could make sure that the images include a recent enough cloud-init as the sister bug to this in cloud-init has been marked fixed for 0.7.7, while the image only has 0.7.5 in there IIRC.