Comment 23 for bug 1410876

It looks like the lxc commands that juju uses aren't logged at DEBUG log level. It would be really helpful for debugging this if they were.

For example, from the error here, it's not clear what 'lxc-clone' command is being called:

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

Where is the "%s" coming from? Either lxc or juju is not converting a format specifier and it's not clear which. Logging what lxc commands juju calls would clear that up.