Juju vagrant box failed to start (wily)

[Bruno Ranieri]

The Vagrant Boxes provided via https://jujucharms.com/docs/stable/config-vagrant does not start-up as promised.
According to the documentation it is possible to access the Juju-Gui after start-up, this fails due to an error.

Steps to reproduce:
--------------------------
$ mkdir JujuBox
$ cd JujuBox
$ vagrant box add JujuBox https://cloud-images.ubuntu.com/vagrant/wily/current/wily-server-cloudimg-amd64-juju-vagrant-disk1.box
$ vagrant init JujuBox
$ vagrant up

Yields the output, with error: '/tmp/jujuredir/setup-juju.sh: line 86: start: command not found' (and line 88)
--------------------------------------------------------------------------------------------------------------------------------------------------
[...]
==> default: Bootstrapping Juju...
==> default: Bootstrapping environment "local"
==> default: Starting new instance for initial state server
==> default: Building tools to upload (1.25.3.1-wily-amd64)
==> default: Installing Juju agent on bootstrap instance
==> default: Logging to /home/vagrant/.juju/local/cloud-init-output.log on remote host
==> default: Installing package: curl
==> default: Installing package: cpu-checker
==> default: Installing package: bridge-utils
==> default: Installing package: rsyslog-gnutls
==> default: Installing package: cloud-utils
==> default: Installing package: cloud-image-utils
==> default: Installing package: tmux
==> default: Bootstrapping Juju machine agent
==> default: Starting Juju machine agent (juju-agent-vagrant-local)
==> default: Bootstrap agent installed
==> default: -> local
==> default: Waiting for API to become available
==> default: Waiting for API to become available
==> default: Waiting for API to become available
==> default: Bootstrap complete
==> default: Taking a nap to let state server come up...
==> default: Added charm "cs:trusty/juju-gui-45" to the environment.
==> default: Setting up Juju GUI dependencies...this may take a minute.
==> default: You can find the log in /var/log/juju-setup.log
==> default: You have not informed bzr of your Launchpad ID, and you must do this to
==> default: write to Launchpad or access private data. See "bzr help launchpad-login".
==> default: Branched 25 revisions.
==> default: Taking a nap to let Juju Gui get setup
==> default: Traceback (most recent call last):
==> default: File "/root/redirect.py", line 10, in <module>
==> default: from cloudinit import util as ciutil
==> default: ImportError: No module named cloudinit
==> default: /tmp/jujuredir/setup-juju.sh: line 86: start: command not found
==> default: /tmp/jujuredir/setup-juju.sh: line 88: status: command not found
[...]
Juju GUI: To access the Juju GUI, point your browser at:
      http://127.0.0.1:6079
      Username: admin
      Password: *******

Checking with netstat there is no port open (including port 6080 from the outdated documentation).

Juju fail to finish the deployment of the service:

$ juju status
environment: local
machines:
  "0":
    agent-state: started
    agent-version: 1.25.3.1
    dns-name: localhost
    instance-id: localhost
    series: wily
    state-server-member-status: has-vote
  "1":
    agent-state: started
    agent-version: 1.25.3.1
    dns-name: 10.0.3.180
    instance-id: vagrant-local-machine-1
    series: trusty
    hardware: arch=amd64
services:
  juju-gui:
    charm: cs:trusty/juju-gui-45
    exposed: true
    service-status:
      current: unknown
      message: Waiting for agent initialization to finish
      since: 01 Feb 2016 15:35:53Z
    units:
      juju-gui/0:
        workload-status:
          current: unknown
          message: Waiting for agent initialization to finish
          since: 01 Feb 2016 15:35:53Z
        agent-status:
          current: allocating
          since: 01 Feb 2016 15:35:53Z
        agent-state: pending
        machine: "1"
        public-address: 10.0.3.180

Output of
$ juju debug-log --replay >> /vagrant/juju-debug-log.log
is attached.