Comment 1 for bug 1423626

The problem in such cases is juju has little control on how the machine's hardware (as seed by lshw) changes between commissioning and deployment, and frankly neither has maas.

jamespage suggested that juju could "inject" a script very early (e.g. a bootcmd) in the cloud-init userdata to try and discover what interface names and MAC addresses the machine has and try to match those from the lshw data juju already gets from maas during node allocation. This nice thing about this solution is that it's not maas specific, but can be used elsewhere (e.g. other distros, with systemd, etc.).