The problem with running scripts like that is this is all coming from an automated environment that cleans up after failure. We haven't been able to add a script to do that yet.
Did see another failure of this that has a slightly different error message: agent-state-info: 'container failed to start and failed to destroy: manual
cleanup of containers needed: error executing "lxc-wait": lxc_container:
utils.c: mkdir_p: 220 Not a directory - failed to create directory ''/run/lock/lxc//var/lib/lxc/juju-machine-4-lxc-1/snaps''; lxc_container: lxccontainer.c: do_snapshot_destroy: 3272 Could not destroy
snapshot %s - failed to allocate a pty; Insufficent privileges to control juju-machine-4-lxc-1'
The problem with running scripts like that is this is all coming from an automated environment that cleans up after failure. We haven't been able to add a script to do that yet.
Did see another failure of this that has a slightly different error message:
agent- state-info: 'container failed to start and failed to destroy: manual lock/lxc/ /var/lib/ lxc/juju- machine- 4-lxc-1/ snaps'' ;
lxc_ container: lxccontainer.c: do_snapshot_ destroy: 3272 Could not destroy
juju- machine- 4-lxc-1'
cleanup of containers needed: error executing "lxc-wait": lxc_container:
utils.c: mkdir_p: 220 Not a directory - failed to create directory ''/run/
snapshot %s - failed to allocate a pty; Insufficent privileges to control