In my environment, juju lxc nodes in local provider get the same MAC and IP address.
# grep -r lxc.network.hwaddr /var/lib/lxc/*/config
/var/lib/lxc/juju-trusty-template/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
/var/lib/lxc/nobuto-local-machine-1/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
/var/lib/lxc/nobuto-local-machine-2/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
/var/lib/lxc/nobuto-local-machine-3/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
/var/lib/lxc/nobuto-local-machine-4/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
/var/lib/lxc/nobuto-local-machine-5/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
/var/lib/lxc/nobuto-local-machine-6/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
/var/lib/lxc/nobuto-local-machine-7/config:lxc.network.hwaddr = 00:16:3e:11:a8:70
$ sudo lxc-ls -f
NAME STATE IPV4 IPV6 GROUPS AUTOSTART
-------------------------------------------------------------------------
juju-trusty-template STOPPED - - - NO
nobuto-local-machine-1 RUNNING 192.168.123.203 - - YES
nobuto-local-machine-2 RUNNING 192.168.123.203 - - YES
nobuto-local-machine-3 RUNNING 192.168.123.203 - - YES
nobuto-local-machine-4 RUNNING 192.168.123.203 - - YES
nobuto-local-machine-5 RUNNING 192.168.123.203 - - YES
nobuto-local-machine-6 RUNNING 192.168.123.203 - - YES
nobuto-local-machine-7 RUNNING 192.168.123.203 - - YES
~/.juju/environments.yaml
local:
type: local
apt-http-proxy: 'http://10.0.7.2:8000/'
lxc-clone-aufs: true
network-bridge: 'virbr0'
juju-core:
Installed: 1.20.1-0ubuntu1~14.10.1~juju1
juju-local:
Installed: 1.20.1-0ubuntu1~14.10.1~juju1
It looks like a issue in lxc-clone. I will opened a bug against lxc package instead. /bugs.launchpad .net/ubuntu/ +source/ lxc/+bug/ 1346815
https:/