Exactly the same issue with
$ juju init
# edit .juju/environments.yaml to select trusty as default release, and default
to "local"
$ juju bootstrap
uploading tools for series [utopic precise trusty]
Logging to /home/martin/.juju/local/cloud-init-output.log on remote host
Starting MongoDB server (juju-db-martin-local)
Bootstrapping Juju machine agent
Starting Juju machine agent (juju-agent-martin-local)
$ juju deploy juju-gui
Added charm "cs:trusty/juju-gui-2" to the environment.
$ juju status
environment: local
machines:
"0":
agent-state: started
agent-version: 1.18.4.1
dns-name: localhost
instance-id: localhost
series: utopic
"1":
agent-state: started
agent-version: 1.18.4.1
dns-name: 10.0.3.104
instance-id: martin-local-machine-1
series: trusty
hardware: arch=amd64
services:
juju-gui:
charm: cs:trusty/juju-gui-2
exposed: false
units:
juju-gui/0:
agent-state: pending
agent-version: 1.18.4.1
machine: "1"
public-address: 10.0.3.104
.juju/local/log/unit-juju-gui-0.log now loops on teh same git error.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1329051
Title:
local boostrapping of juju-gui fails on "git not found"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1329051/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
