I have a MAAS server and a JUJU server (not included on MAAS); I'm trying to bootstrap a node to create a MAAS controller with its models.

I execute the following:

juju bootstrap maas-hw openstackub --config=./maas-hw-config.yaml --constraints="tags=ctrl" --config bootstrap-timeout=1800

and here's the output:

Creating Juju controller "openstackub" on maas-hw

Looking for packaged Juju agent version 2.0.2 for amd64

Launching controller instance(s) on maas-hw...

  kbsp3n (arch=amd64 mem=4G cores=1)

Fetching Juju GUI 2.2.7

Waiting for address

Attempting to connect to

Attempting to connect to

Logging to /var/log/cloud-init-output.log on the bootstrap machine

Running apt-get update

Installing curl, cpu-checker, bridge-utils, cloud-utils, tmux

Fetching Juju agent version 2.0.2 for amd64

And here I am waiting for hours to finish the fetching thing.

I cannot connect to the deployed node in any way because it hasn't finished deployment and cannot see any log.

The JUJU srv has internet access and network access to node via the 2 network interfaces. The node appears as deployed at MAAS. If I ctrl + C the juju command, it fails with error 130 and the node revert to READY node.

What am I missing?

Thank you in advanced!!! Jorge

closed as off-topic by Stefano Palazzo Dec 21 '16 at 13:32

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This describes a problem that can't be reproduced that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – Stefano Palazzo
If this question can be reworded to fit the rules in the help center, please edit the question.

Browse other questions tagged or ask your own question.