Public bug reported:
I am on current Utopic, and installed the utopic-proposed juju packages
(as 1.18.1 is known to not work on utopic):
ii juju-core 1.18.4-0ubuntu1 amd64 Juju is devops distilled - client
ii juju-local 1.18.4-0ubuntu1 all dependency package for the Juju local provider
ii juju-mongodb 2.4.10-0ubuntu1 amd64 MongoDB object/document-oriented database
for Juju
ii juju-quickstart 1.3.1-0ubuntu1 all Easy configuration of Juju environments
ii python-jujuclient 0.17.5-0ubuntu2 all Python API client for juju
With no pre-existing ~/.juju, and a workaround for bug 1329049,
quickstart does this:
$ juju quickstart
juju quickstart v1.3.1
bootstrapping the local environment (type: local)
sudo privileges will be required to bootstrap the environment
retrieving the environment status
retrieving the Juju API address
connecting to wss://10.0.3.1:17070
requesting juju-gui deployment
charm URL: cs:precise/juju-gui-90
juju-gui deployment request accepted
exposing service juju-gui
requesting new unit deployment
juju-gui/0 deployment request accepted
juju-gui/0 deployment is pending
machine 1 provisioning is pending
juju-gui/0 placed on 10.0.3.219
machine 1 is started
and now hangs eternally.
$ 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.219
instance-id: martin-local-machine-1
series: precise
hardware: arch=amd64
services:
juju-gui:
charm: cs:precise/juju-gui-90
exposed: true
units:
juju-gui/0:
agent-state: pending
agent-version: 1.18.4.1
machine: "1"
public-address: 10.0.3.219
unit-juju-gui-0.log shows an endless stream of
2014-06-11 20:03:18 ERROR juju.worker.uniter.charm git.go:211 git command
failed: exec: "git": executable file not found in $PATH
path:
/var/lib/juju/agents/unit-juju-gui-0/state/deployer/update-20140611-220318576432597
args: []string{"init"}
2014-06-11 20:03:18 WARNING juju.worker.uniter.charm git_deployer.go:200 no
current staging repo
2014-06-11 20:03:18 ERROR juju.worker.uniter.filter filter.go:116 tomb: dying
2014-06-11 20:03:18 ERROR juju runner.go:220 worker: exited "uniter":
ModeInstalling cs:precise/juju-gui-90: git init failed: exec: "git": executable
file not found in $PATH
So apparently the charm is missing to install git?
Also, is it really on purpose that juju-gui-0 runs on precise, not on
trusty? Even with a pre-existing .juju/environments.yaml with "default-
series: trusty" in the local section it does that.
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: juju-core 1.18.4-0ubuntu1 [origin: unknown]
ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8
Uname: Linux 3.15.0-5-generic x86_64
ApportVersion: 2.14.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jun 11 22:01:09 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-27 (104 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224)
SourcePackage: juju-core
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: juju-core (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug third-party-packages utopic
--
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
