juju bootstrap fails on HP Cloud unless tools are already uploaded

Bug #1275282 reported by Evan
6
This bug affects 1 person
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://bugs.launchpad.net/juju-core/+bug/1275280). Unless I've run sync-tools (or presumably used --upload-tools) before bootstrapping, I get the following error every time with a new account on HP Cloud (Compute v13.5).

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://region-a.geo-1.objects.hpcloudsvc.com/v1/11289530460295/images

Output from juju bootstrap:

rm -rf '/var/lib/juju/agents/bootstrap'
ln -s 1.17.0-precise-amd64 '/var/lib/juju/tools/machine-0'
echo 'Starting Juju machine agent (jujud-machine-0)' >&9
cat >> /etc/init/jujud-machine-0.conf << 'EOF'
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/juju/tools/machine-0/jujud machine --data-dir '/var/lib/juju' --machine-id 0 --debug >> /var/log/juju/machine-0.log 2>&1
EOF

start jujud-machine-0
) >> /var/log/cloud-init-output.log 2>&1
sudo: unable to resolve host juju-hp-machine-0
Logging to /var/log/cloud-init-output.log on remote host
Installing add-apt-repository
Adding apt repository: deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/cloud-tools main
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://streams.canonical.com/juju/tools/releases/juju-1.17.0-precise-amd64.tgz'
2014-02-01 16:07:10 ERROR juju.provider.common bootstrap.go:140 bootstrap failed: exit status 1
Stopping instance...
2014-02-01 16:07:10 DEBUG juju.provider.openstack provider.go:834 terminating instances [cb19e358-5379-4dd2-93a9-8d5669c95243]
2014-02-01 16:07:13 ERROR juju.cmd supercommand.go:294 exit status 1

Evan (ev)
affects: juju → juju-core
description: updated
Revision history for this message
Curtis Hovey (sinzui) wrote :

This issue was fixed in the 1.17.1 devel release. the current devel release is 1.17.2

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.