initial deploy using local provider fails because template creation takes too long

[Ricardo Kirkner]

When running juju-core using the local provider on a clean trusty image on canonistack (flavor=1137) after bootstrapping the environment the first deployment fails while creating the template container.

Steps to reproduce:

- create an instance on canonistack lcy02 region

- deploy a unit
juju bootstrap
juju deploy wordpress

After a time (10 minutes more or less) juju status looks like

$ juju status
environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.18.1.1
    dns-name: localhost
    instance-id: localhost
    series: trusty
  "1":
    agent-state-info: '(error: template container "juju-precise-template" did not
      stop)'
    instance-id: pending
    series: precise
services:
  wordpress:
    charm: cs:precise/wordpress-21
    exposed: false
    relations:
      loadbalancer:
      - wordpress
    units:
      wordpress/0:
        agent-state: pending
        machine: "1"

$ lxc-ls --fancy
NAME STATE IPV4 IPV6 AUTOSTART
----------------------------------------------------------
juju-precise-template RUNNING 10.0.3.14 - NO

[Curtis Hovey (sinzui)]

This issue happens because canonistack is over resourced. This situation would be intolerable on properly resourced clouds or real hardware.

[Ricardo Kirkner (ricardokirkner)]

After the UOS session on using the local provider, I've started using the juju-clean plugin, and this solved all the issues I was having with the local provider on my laptop (the problem was evidently some unclean state left over, quite possibly some very old cloud images in the cache). I haven't checked again on canonistack, as I can now work on my laptop again.