Juju fails to bootstrap on a private OpenStack cloud due to not finding image metadata

Bug #1420155 reported by Muntaner on 2015-02-10
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Undecided
Unassigned

Bug Description

Scenario: I have a private OpenStack cloud, with all the components installed on a single server. The components (glance, swift, etc.) communicate via a private LAN.

I'm able to log and ssh to the OpenStack machine via LAN (10.0.0.0/24), can access without problems the horizon dashboard, and ping/ssh to the VMs instances of OpenStack via floating IPs: these VMs are able to ping/ssh with the outer devices, such as my laptop and other PCs connected to the same LAN.

So I tried to use Juju with my laptop to deploy software on my private OpenStack cloud, but the bootstrap fails due to not finding the images metadata.

I generated those metadata via juju metadata generate-image in a folder juju-tools, validated them, and tried to bootstrap with:

juju bootstrap --metadata-source /home/mike/juju-tools --upload-tools --debug

So, juju is able to communicate with OpenStack: actually a VM with Ubuntu Cloud is instanced, and this instance uses apt-get stuff, updates and so on, but Juju suddenly fails to bootstrap due to not finding the metadatas just after starting MongoDB.

Related log:
http://paste.ubuntu.com/10143346/

So, seems like --metadata-source /home/mike/juju-tools isn't able to properly upload the metadatas to the destination.

My workaround (suggested by fwereade): in my laptop, go in the folder where the metadatas have been generated with a terminal and run:

python -m SimpleHTTPServer <free port>

This will render the metadatas accessible via HTTP.
To tell this to Juju, modify the environments.yawl and add this line:

image-metadata-url: http://10.0.0.154:<used port with SimpleHTTPServer>/images

Where 10.0.0.154 is the IP in the LAN of the computer where the metadatas are (in my scenario, my laptop).

This will tell Juju to access the metadatas via this URL, and the bootstrap will success.

In my opinion, actually the logs aren't very helpful to diagnose this situation: also, I can't understand why the VMs is correctly instantiated in the first phase of the bootstrap, since Juju fails at a certain point to fetch the needed metadatas.

tags: added: openstack
removed: ubuntu-openstack
Curtis Hovey (sinzui) on 2015-02-10
tags: added: metadata-source
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers