Comment 3 for bug 1309805

$ juju version
1.18.1-trusty-amd64

$ juju init
$ juju switch local
$ juju bootstrap
$ juju deploy juju-gui
$ 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: started
    agent-version: 1.18.1.1
    dns-name:
    instance-id: seppel-local-machine-1
    series: trusty
    hardware: arch=amd64
services:
  juju-gui:
    charm: cs:trusty/juju-gui-1
    exposed: false
    units:
      juju-gui/0:
        agent-state: started
        agent-version: 1.18.1.1
        machine: "1"
        open-ports:
        - 80/tcp
        - 443/tcp
        public-address:

then after:

$ juju deploy owncloud (or another charm like mysql)
$ juju status

environment: local
machines:
...
  "4":
    instance-id: pending
    series: precise
services:
 ...
  owncloud:
    charm: cs:precise/owncloud-13
    exposed: false
    units:
      owncloud/0:
        agent-state: pending
        machine: "4

$ tail .juju/local/log/all-machines.log

machine-0: 2014-04-21 13:58:13 ERROR juju runner.go:220 worker: exited "environ-provisioner": failed to process updated machines: cannot start machine 4: no matching tools available

tools-metadata-url in .juju/environments/local.jenv is set to: tools-metadata-url: ""