juju bootstrap fails on HP Cloud unless tools are already uploaded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not sure if this is strictly a bug, usability issue, or fallout from newer accounts on HP Cloud not having access to the right metadata (https:/
I did have the image metadata synced to a public bucket I created for it, but did not have the tools in there as well:
image-metadata-url: https:/
Output from juju bootstrap:
rm -rf '/var/lib/
ln -s 1.17.0-
echo 'Starting Juju machine agent (jujud-machine-0)' >&9
cat >> /etc/init/
description "juju machine-0 agent"
author "Juju Team <email address hidden>"
start on runlevel [2345]
stop on runlevel [!2345]
respawn
normal exit 0
limit nofile 20000 20000
exec /var/lib/
EOF
start jujud-machine-0
) >> /var/log/
sudo: unable to resolve host juju-hp-machine-0
Logging to /var/log/
Installing add-apt-repository
Adding apt repository: deb http://
Running apt-get update
Running apt-get upgrade
Installing package: git
Installing package: cpu-checker
Installing package: mongodb-server
Fetching tools: wget --no-verbose -O $bin/tools.tar.gz 'https:/
2014-02-01 16:07:10 ERROR juju.provider.
Stopping instance...
2014-02-01 16:07:10 DEBUG juju.provider.
2014-02-01 16:07:13 ERROR juju.cmd supercommand.go:294 exit status 1
affects: | juju → juju-core |
description: | updated |
This issue was fixed in the 1.17.1 devel release. the current devel release is 1.17.2