Ask Your Question
0

juju bootstrap failed

asked 2015-01-29 00:57:44 -0600

rizka gravatar image

I use MAAS to make landscape openstack autopilot and use sudo openstack-install but it's failed. This is my command.log

INFO • 01-26 13:43:19 [LINE:156, FUNC: ] • cloudinstall • cloud-install starting with options: Namespace(arch=None, edit_placement=False, extra_ppa=None, install_only=False, killcloud=False, release=None, uninstall=False, upstream_deb=None, with_maas_address=None, with_maas_apikey=None) DEBUG • 01-26 13:43:19 [LINE:111, FUNC:main_loop] • cloudinstall.install • loop's screen is INFO • 01-26 13:43:19 [LINE:71, FUNC:status_context] • cloudinstall.core • Get started by entering an OpenStack password for your cloud DEBUG • 01-26 13:43:19 [LINE:93, FUNC:_build_widget] • cloudinstall.ui.dialog • Num items: 2, items: DEBUG • 01-26 13:43:29 [LINE:111, FUNC:submit] • cloudinstall.ui.dialog • Callback on : OrderedDict([('password', ), ('confirm_password', )]) INFO • 01-26 13:43:29 [LINE:71, FUNC:status_context] • cloudinstall.core • Choose your installation path DEBUG • 01-26 13:43:53 [LINE:214, FUNC:submit] • cloudinstall.ui • Callback on : OrderedDict([('Landscape OpenStack Autopilot', (, 'Benefit from best practices in cloud building, and get up and running within minutes, all from an intuitive web UI.')), ('Multi', (, 'OpenStack installation utilizing MAAS.')), ('Single', (, 'Fully containerized OpenStack installation on a single machine.'))]) INFO • 01-26 13:43:53 [LINE:71, FUNC:status_context] • cloudinstall.core • Please enter your Landscape information and MAAS Server IP and API Key. Use the MAAS web UI or 'maas list' to find your API Key DEBUG • 01-26 13:43:53 [LINE:93, FUNC:_build_widget] • cloudinstall.ui.dialog • Num items: 4, items: DEBUG • 01-26 13:45:08 [LINE:111, FUNC:submit] • cloudinstall.ui.dialog • Callback on : OrderedDict([('admin_email', ), ('admin_name', ), ('maas_server', ), ('maas_apikey', )]) DEBUG • 01-26 13:45:08 [LINE:81, FUNC:_save_lds_creds] • cloudinstall.landscape_install • Existing MAAS defined, doing a LDS installation with existing MAAS. INFO • 01-26 13:45:08 [LINE:71, FUNC:status_context] • cloudinstall.core • Waiting for sufficient resources in MAAS DEBUG • 01-26 13:45:11 [LINE:650, FUNC:ssh_genkey] • cloudinstall.utils • ssh keys exist for this user, they will be used instead. If the current ssh keys are not passwordless you'll be required to enter your ssh key password during container creation. INFO • 01-26 13:45:11 [LINE:71, FUNC:status_context] • cloudinstall.core • Bootstrapping Juju DEBUG • 01-26 13:45:11 [LINE:139, FUNC:do_install] • cloudinstall.multi_install • Bootstrapping Juju: JUJU_HOME=/home/ubuntu/.cloud-install juju bootstrap DEBUG • 01-26 14:45:32 [LINE:145, FUNC:do_install] • cloudinstall.multi_install • Problem during bootstrap: '{'status': 1, 'output': 'Launching instance\nWARNING picked arbitrary tools &{1.20.14-trusty-amd64 https://streams.canonical.com/juju/to... ad7360aa5512b8d7cc1ad0ceb223bd9a1c8f5c6b0b131b5a3bd8fde623b85585 8130261}\n - /MAAS/api/1.0/nodes/node-fc4112b0-a203-11e4-8c5f-1c6f65cc39f5/\nWaiting for address\nAttempting to connect to 4r74w.maas:22\nAttempting to connect to 4r74w.maas:22\nAttempting to connect to 192.168.0.206:22\nERROR bootstrap failed: waited for 1h0m0s without being able to connect: /var/lib/juju/nonce.txt does not exist\nStopping instance...\nBootstrap failed, destroying environment\nERROR waited for 1h0m0s without being able to connect: /var/lib/juju/nonce.txt does not exist\n'}' DEBUG • 01-26 14:45:32 [LINE:51, FUNC:global_exchandler] • cloudinstall.utils • Traceback (most recent call last ...

(more)
edit retag flag offensive close merge delete

1 answer

Sort by » oldest newest most voted
0

answered 2015-10-21 17:06:03 -0600

ubchaudhry gravatar image

Edit the file here:

sudo nano /etc/sysctl.conf

Un-comment this line:

net.ipv4.ip_forward=1

Now reboot MAAS and try the install again.

If that doesn't work try updating IPtables on MAAS with something like this:

sudo iptables -A FORWARD -o eth0 -i eth1 -s 10.1.1.0/24 -m conntrack --ctstate NEW -j ACCEPT sudo iptables -A FORWARD -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT sudo iptables -t nat -F POSTROUTING sudo iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

sudo iptables-save | sudo tee /etc/iptables.sav

Edit /etc/rc.local and add the following lines before the "exit 0" line:

iptables-restore < /etc/iptables.sav

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2015-01-29 00:57:44 -0600

Seen: 867 times

Last updated: Oct 21 '15