juju-quickstart

openstack trusty:liberty deployment fails due to no relations and insufficient peer units

Bug #1639170 reported by Benedikt Troester on 2016-11-04

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	juju-core	Invalid	Undecided	Unassigned
	juju-quickstart	New	Undecided	Unassigned

Bug Description

Hi all!

I'm currently trying to deploy an Openstack trusty-liberty cloud with juju (1.25.6-0ubuntu1.14.04.1) in a KVM virtualized MAAS environment. To do so, I downloaded the openstack-base bundle from here: https://jujucharms.com/openstack-base/
Then modified each charm repo "charm: cs:XXX" to match the trusty release, changed the series to trusty and chose cloud:trusty-liberty as the openstack-origin.

Now what happens after "juju quickstart bundle.yaml --no-browser" is that deployment works, but relations are not established as well as some services do not get spawned. Apparently I have not enough peers defined in my MAAS env., but I currently have 6 VMs running:
1 for MAAS
1 for juju
4 Nodes (all defined in MAAS).
Additionally there is an other unused Node in MAAS, which is not being allocated at all.
Each VM has 2 NATed Networks (both are managed in MAAS), 8GB RAM, 1 Core, 60 + 20G HDD, VMX is forwarded to the machines.

My question now is: why does this fail?

I've attached my bundle.yaml, juju status and juju debug-log output.

See original description

Revision history for this message

Benedikt Troester (btroester) wrote on 2016-11-04:

data Edit (4.6 KiB, application/x-tar)

description:

updated

Revision history for this message

James Tunnicliffe (dooferlad) wrote on 2016-11-08:

I am sorry to say that all I can see from the logs is Juju reporting that the reality it sees is indeed not what the charms want, that is ceph-mon doesn't have sufficient peers. Some charmers should be coming this way to help who, I would hope, have already charmed the trusty:liberty case. I had a dig through the charms history on both Git and Bazaar for that combination and didn't find anything, though perhaps I didn't dig hard enough.

I believe that the charms are now targeting Juju 2.0 with LXD rather than 1.25 and LXC, though I would be surprised if we had dropped compatibility.

https://jujucharms.com/openstack-base/ has a link to submit a bug against the charm (https://github.com/openstack-charmers/openstack-bundles/issues) or you could try #juju on freenode (https://webchat.freenode.net/ if you don't have an IRC client at the ready).

Revision history for this message

James Page (james-page) wrote on 2016-11-08:

The bundle (openstack-base) should support either 1.25.6 or 2.0 (via the native bundle support in this version of Juju). For 1.25.6 you have to use one of the other bundle deployment tools such as juju-deployer or quickstart - our automated CI runs using juju-deployer for 1.25.6.

It looks like juju quickstart failed to deploy/place a number of services, hence the resulting service status of blocked for most services.

Anastasia (anastasia-macmood) on 2016-11-10