jamespages, myself and Murali were discussing the issue on #juju and it turned out the problem is most likely caused by using the debian installer to deploy the nodes in maas, rather than the fast installer. The former sets the "biosdevname" apt policy which leads to renaming ethX interfaces to emX, unlike the latter.
I'm investigating now on my local kvm-based maas:
1. disabling "use fast installer" on previously commissioned node and bootstrapping juju on it
2. disabling the fast installer, recommissioning the node and then deploying
Related bug #1423626
jamespages, myself and Murali were discussing the issue on #juju and it turned out the problem is most likely caused by using the debian installer to deploy the nodes in maas, rather than the fast installer. The former sets the "biosdevname" apt policy which leads to renaming ethX interfaces to emX, unlike the latter.
I'm investigating now on my local kvm-based maas:
1. disabling "use fast installer" on previously commissioned node and bootstrapping juju on it
2. disabling the fast installer, recommissioning the node and then deploying
I'll update the bug with my results.