Comment 3 for bug 1410876

I took a look and requested oil team to try to reproduce this in newer versions and different configurations (lxc-use-clone:false) to try to determine where exactly lies the problem.

The relevant line on the logs is:

juju_debug_log.txt:machine-5: 2015-01-15 11:41:05 ERROR juju.container.lxc lxc.go:208 lxc container cloning failed: error executing "lxc-clone": lxc_container: utils.c: mkdir_p: 220 Not a directory - failed to create directory '/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'; lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges to control juju-trusty-lxc-template

and

2015-01-15 11:41:05 ERROR juju.provisioner provisioner_task.go:418 cannot start instance for machine "5/lxc/0": error executing "lxc-clone": lxc_container: utils.c: mkdir_p: 220 Not a directory - failed to create directory '/run/lock/lxc//var/lib/lxc/juju-trusty-lxc-template/snaps'; lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy snapshot %s - failed to allocate a pty; Insufficent privileges to control juju-trusty-lxc-template

After checking the code I found out that the clone operation error ouput is relayed directly from golxc.Clone I cannot determine exactly what is going on there.

Just in case the error could be in a path I checked http://bazaar.launchpad.net/~juju/golxc/trunk/revision/8 which adds containerDir to the cloning but obtained no useful conclusion.