pyjuju

Cannot bootstrap stock ubuntu AMIs

Bug #807281 reported by Adam Gandelman on 2011-07-07

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	pyjuju	Invalid	Undecided	Unassigned	pyjuju dublin

Bug Description

When attempting to use an oneiric AMI or a stock natty AMI, ensemble cannot bootstrap.

The generated cloud-init runcmd script does not create the bzr repositories in /usr/lib/ensemble/ensemble and /usr/lib/ensemble/txzookeeper before attempting to pull the latest commits. As result, the following fails and blocks the entire bootstrap process:

#!/bin/sh
sudo mkdir -p /usr/lib/ensemble
cd /usr/lib/ensemble/ensemble && sudo /usr/bin/bzr up

It appears the default AMI used by ensemble already has had these branches cloned before the AMI was bundled.

Revision history for this message

Adam Gandelman (gandelman-a) wrote on 2011-07-07:

/var/lib/cloud/instance/scripts/runcmd after cloud-init has run Edit (875 bytes, text/plain)

Revision history for this message

Adam Gandelman (gandelman-a) wrote on 2011-07-08:

Seem to have some issues with the natty mirror in us-east right now. The following patch allows me to bootstrap stock AMIs just fine in the meantime.

Revision history for this message

Adam Gandelman (gandelman-a) wrote on 2011-07-08:

bootstrap.patch Edit (1.3 KiB, text/plain)

Revision history for this message

Kapil Thangavelu (hazmat) wrote on 2011-07-11:

afaics this bug and patch are against an older version of the codebase, the merge of sans-ami (july 8th, 2011) allows for standard ubuntu amis.

the patch references some 'bzr up' logic, ensemble doesn't do bzr up anymore.. it either does the bzr checkout, or defaults to installing from ppa on the environment machines. it looks like your local installation might be out of date.